Enterprise Vault™ Utilities
- About this guide
- ArchivePoints
- Audit Viewer
- Backtrace
- CenteraPing
- Domino Archive Exporter
- Domino Profile Document Tool
- Domino Retention Plan Tool
- DTrace
- EVDominoExchangeMigration Tool
- Running the EVDominoExchangeMigration tool
- EVDuplicateCleaner
- EVEARemovalUtility
- EVFSASetRightsAndPermissions
- EVrights
- EVservice
- EVSPShortcutManager
- EVSVR
- About EVSVR
- About the EVSVR operation settings
- Using the output from one EVSVR operation as input for another operation
- Viewing the EVSVR output log file
- Running EVSVR in interactive mode
- FSARunNow
- FSAUndelete
- FSAUtility
- NTFS to Centera Migration
- Permissions Browser
- Policy Manager (EVPM)
- Sections and keynames in Policy Manager initialization file
- Policy Manager initialization file examples
- About using the Provisioning API to run Policy Manager scripts
- ResetEVClient
- Vault Store Usage Reporter
DumpSaveset command
The DumpSaveset command retrieves the saveset and associated SIS parts of the specified archived item.
DumpSaveset EntryId SavesetId [-o OutputFolder]
Where the parameters are as follows:
EntryId | Identifies the required vault store entry, archive entry, or archive folder entry. EVSVR uses this to determine the location of the saveset. |
SavesetId | Specifies the required saveset ID or transaction ID. |
OutputFolder | Specifies the path to the folder in which to store the retrieved files and log file. By default, this is the |
In the following example, the two parameters specify the vault store entry ID and saveset transaction ID of the required saveset:
ds 1995C3ACBB9472646AB0F3A0FDC7066B91210000testsrv1.domain.local 713C88D67D80E8046FFF279AE27D46B1
This command does not specify an output folder with the -o parameter, so DumpSaveset outputs the files to the default location, for example C:\Program Files (x86)\Enterprise Vault\Reports\EVSVR
. All DumpSaveset files are output to a time-stamped folder under this output folder, such as EVSVR_DumpSaveset_20100714181917
. So, in this example, the full output path is as follows:
C:\Program Files (x86)\Enterprise Vault\Reports\EVSVR\EVSVR_DumpSaveset_20100714181917
Except where noted, DumpSaveset outputs all the files and folders that are described below.
Table: Files and folders that are directly under the full output path
Output | Description |
---|---|
Log | This is the log file. In the example above, its file name is Always review the log file to determine how successful the operation was. The file shows any errors that occurred. |
VSDBRecords.xml | This XML file contains the vault store database records for the saveset that DumpSaveset has retrieved. |
Recombined folder | This folder contains the files that Enterprise Vault reconstructs after the entire saveset has been retrieved. See Table: Contents of the Recombined folder. |
Parts folder | This folder contains the files that comprise the retrieved saveset. See Table: Contents of the Parts folder. |
Table: Contents of the Recombined folder
Output | Description |
---|---|
DVS | This file contains all the data related to the retrieved saveset, except where this is a large-file saveset. DumpSaveset outputs large-file data to the
|
DocFile | This file is an uncompressed structured storage version of the above recombined DVS file. You can inspect its contents with a structured storage viewer. Sample file name:
|
Native item | This is the original item that Enterprise Vault retrieved: a Domino message (DVNS) file, Exchange message (MSG) file, IMAP message (EML) file, or the original large file. |
Table: Contents of the Parts folder
Output | Description |
---|---|
DVS/ARCHDVS (if CAB collected or migrated) | This file is either the entire saveset or, where sharing has been enabled, one part of a multipart saveset. Sample file name:
|
DocFile | This file is an uncompressed structured storage version of the above DVS file. You can inspect its contents with a structured storage viewer. Sample file name:
|
DVSSP/ARCHDVSSP (if CAB collected or migrated) | Only output for multipart savesets where sharing has been enabled. The files are not generated for savesets that are stored on a Centera device. Sample file name: |
DVSCC/ARCHDVSCC (if CAB collected or migrated) | Only output for multipart savesets where sharing has been enabled and converted content has been generated. The files are not generated for savesets that are stored on a Centera device. Sample file name:
|
DVFSP/ARCHDVFSP (if migrated) | Only output for large-file multipart savesets where sharing has been enabled. The files are not generated for savesets that are stored on a Centera device. Sample file name: |
DVF/ARCHDVF (if migrated) | Only output for large-file savesets where sharing has not been enabled. The files can also be generated for savesets that are stored on a Centera device. Sample file name:
|
DVFCC/ARCHDVFCC (if migrated) | Only output for large-file savesets where sharing has not been enabled and where converted content has been generated. The files are not generated for savesets that are stored on a Centera device. Sample file name: |
CAB/ARCHCAB (if migrated) | Only output when parts of the retrieved saveset are stored on CIFS partitions that have been configured for collection using CAB files. DumpSaveset outputs a CAB file for each collected part of the saveset. The name of the CAB file has the form
|
CDF.xml | Only output for savesets that are stored on Centera devices. The XML file uses the Clip-Id related to the retrieved saveset as its file name. For example:
|
MetaData.xml | Only output for savesets that have parts that are stored on streamer devices. DumpSaveset outputs an XML file for each part of the saveset. Sample file name:
|
More Information