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
ListSavesetLocations command
The ListSavesetLocations command lists the locations where Enterprise Vault has stored all the parts of the specified saveset.
ListSavesetLocations 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 parameters specify the vault store entry ID and saveset transaction ID of the required saveset, and the folder in which to output the results:
ls 1995C3ACBB9472646AB0F3A0FDC7066B91210000testsrv1.domain.local 713C88D67D80E8046FFF279AE27D46B1 -o c:\MyOutputFolder
If the output folder does not exist, ListSavesetLocations creates it. All ListSavesetLocations files are output to a time-stamped folder under this output folder, such as EVSVR_ListSavesetLocations_20100715112935. So, in this example, the full output path is as follows:
C:\MyOutputFolder\EVSVR_ListSavesetLocations_20100715112935
Table: Files 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. |
More Information