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- About the EVDominoExchangeMigration tool
- Client requirements for the EVDominoExchangeMigration tool
- Adding the EVDominoExchangeMigration tool to the Windows Server firewall exceptions list
- EVDominoExchangeMigration tool and Binary Tree
- Using Quest Notes Migrator for Exchange and the EVDominoExchangeMigration tool
- Requirements for other migration software with the EVDominoExchangeMigration tool
- Running the EVDominoExchangeMigration tool
 
- EVDuplicateCleaner
- EVEARemovalUtility
- EVFSASetRightsAndPermissions
- EVrights
- EVservice
- EVSPShortcutManager
- EVSVR- About EVSVR
- Starting EVSVR
- EVSVR commands
- EVSVR application states
- Creating an EVSVR operation file
- Editing an EVSVR operation file in which you have enabled checkpointing
- Running an EVSVR operation
- 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
- Improving EVSVR performance when processing CAB collections
 
- FSARunNow
- FSAUndelete
- FSAUtility
- NTFS to Centera Migration- About NTFS to Centera Migration
- Managing migrator jobs using NTFS to Centera Migration
- Creating migrator jobs using NTFS to Centera Migration
- Deleting active jobs using NTFS to Centera Migration
- Deleting source files after migration using NTFS to Centera Migration
- NTFS to Centera Migration log files
 
- Permissions Browser
- Policy Manager (EVPM)- About Policy Manager
- Policy Manager syntax
- Saving a Policy Manager initialization file as a Unicode file
- Policy Manager initialization file syntax
- Sections and keynames in Policy Manager initialization file- [Directory] section of the Policy Manager initialization file
- [Archive] section of the Policy Manager initialization file
- [ArchivePermissions] section of the Policy Manager initialization file
- [Filter] section of the Policy Manager initialization file
- [Mailbox] section of the Policy Manager initialization file
- [Folder] section of the Policy Manager initialization file
- [PublicFolder] section in the Policy Manager initialization file
- [PSTdefaults] section in the Policy Manager initialization file
- [PST] section in the Policy Manager initialization file
- [PSTcheckpoint] section in the Policy Manager initialization file
- [NSFDefaults] section in the Policy Manager initialization file
- [NSF] section in the Policy Manager initialization file
- [NSFCheckPoint] section in the Policy Manager initialization file
 
- Policy Manager initialization file examples- Policy Manager initialization file example 1
- Policy Manager initialization file example 2
- Policy Manager initialization file example 3
- Policy Manager initialization file example 4: PST migration
- Policy Manager initialization file example 5: NSF migration
- Policy Manager initialization file example 6: folder permissions
 
- About using the Provisioning API to run Policy Manager scripts
 
- ResetEVClient
- Vault Store Usage Reporter
DumpSISPart command
The DumpSISPart command retrieves the specified SIS part.
DumpSISPart EntryId SisPartId [-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 SIS part. | 
| SisPartId | Identifies the SIS part. | 
| 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 SIS part ID of the required SIS part:
dp 1995C3ACBB9472646AB0F3A0FDC7066B91210000testsrv1.domain.local 714003019523969A1D9431D0592CCE41~91~BAC3E35A~00~1
 This command does not specify an output folder with the -o parameter, so DumpSISPart outputs the files to the default location, for example C:\Program Files (x86)\Enterprise Vault\Reports\EVSVR. All DumpSISPart files are output to a time-stamped folder under this output folder, such as EVSVR_DumpSISPart_20100715114342. So, in this example, the full output path is as follows:
 		C:\Program Files (x86)\Enterprise Vault\Reports\EVSVR\EVSVR_DumpSISPart_20100715114342
Except where noted, DumpSISPart outputs all the files 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. | 
| xml | The XML files contain the vault store database records for the vault stores that reference the SIS part. DumpSISPart generates one XML file for each vault store in the vault store group in which the SIS part resides. Only the XML files for vault stores that reference the SIS part contain information; the others contain an empty EnterpriseVault XML element. Sample file names: 
 
 | 
| DVSSP/ARCHDVSSP (if CAB collected or migrated) | Only output for non-large-file SIS parts. Sample file name: 
 | 
| DVSCC/ARCHDVSCC (if CAB collected or migrated) | Only output for non-large-file SIS parts where converted content has been generated. Sample file name: 
 | 
| DVFSP/ARCHDVFSP (if migrated) | Only output for large-file SIS parts. Sample file name: 
 | 
| DVFCC/ARCHDVFCC (if migrated) | Only output for large-file SIS parts where converted content has been generated. Sample file name: 
 | 
| decompressed | If the SIS part or SIS part converted content file that DumpSISPart has generated was compressed, the command also generates a decompressed version. Sample file names: 
 
 | 
| CAB/ARCHCAB (if migrated) | Only output when the SIS parts are stored
on CIFS partitions that have been configured for collection
using CAB files. A CAB file is expected when the SIS part has been collected. The name of the CAB file has
the form  
 | 
| MetaData.xml | Only output for SIS parts that are stored on streamer devices. DumpSISPart generates one XML file for the SIS part and another for the SIS part converted content that is stored on the streamer device. Sample file names: 
 
 | 
More Information