Search <book_title>...

Veritas Enterprise Vault™ Utilities

Last Published: 2017-07-28

Product(s): Enterprise Vault (12.1)

About this guide
1. About Enterprise Vault utilities
2. Running the Enterprise Vault command-line utilities with administrator privileges
3. Where to get more information about Enterprise Vault
  1. Enterprise Vault training modules
ArchivePoints
1. About ArchivePoints
2. ArchivePoints syntax
3. ArchivePoints examples
Audit Viewer
1. About Audit Viewer
2. Using Audit Viewer to run a report on audit data
3. Copying the search results from Audit Viewer
4. Changing Audit Viewer settings
Backtrace
1. About Backtrace
2. Backtrace default settings
3. Backtrace registry values
4. Backtrace file name format
5. Backtrace examples
CenteraPing
1. About CenteraPing
2. CenteraPing syntax
Domino Archive Exporter
1. About Domino Archive Exporter
2. Domino Archive Exporter syntax
3. Domino Archive Exporter example
Domino Profile Document Tool
1. About Domino Profile Document Tool
2. Domino Profile Document Tool syntax
3. Domino Profile Document Tool examples
Domino Retention Plan Tool
1. About Domino retention plans
2. Domino Retention Plan Tool permissions
3. Defining a Domino retention plan
4. EVDominoRetentionPlans.exe syntax
DTrace
1. About DTrace
2. Running DTrace from the command line
3. Running DTrace from the Administration Console
4. About the DTrace log
5. DTrace troubleshooting
EVDominoExchangeMigration Tool
1. About the EVDominoExchangeMigration tool
2. Client requirements for the EVDominoExchangeMigration tool
3. Adding the EVDominoExchangeMigration tool to the Windows Server firewall exceptions list
4. EVDominoExchangeMigration tool and Binary Tree
5. Using Quest Notes Migrator for Exchange and the EVDominoExchangeMigration tool
6. Requirements for other migration software with the EVDominoExchangeMigration tool
7. Running the EVDominoExchangeMigration tool
EVDuplicateCleaner
1. About EVDuplicateCleaner
2. Prerequisites for EVDuplicateCleaner
3. Configuring EVDuplicateCleaner
4. Running EVDuplicateCleaner
5. Fixing broken shortcuts after you have run EVDuplicateCleaner
EVEARemovalUtility
1. About EVEARemovalUtility
2. EVEARemovalUtility prerequisites
3. Running EVEARemovalUtility
4. EVEARemovalUtility syntax
5. Format of the EVEARemovalUtility output and log files
6. EVEARemovalUtility usage examples
  1. EVEARemovalUtility example: processing a single file
  2. EVEARemovalUtility example: processing a folder and its subfolders
EVFSASetRightsAndPermissions
1. About EVFSASetRightsAndPermissions
2. Running EVFSASetRightsAndPermissions
EVrights
1. About EVrights
2. EVrights syntax
EVservice
1. About EVservice
2. EVservice prerequisites
3. EVservice syntax
4. EVservice list file format
EVSPShortcutManager
1. About EVSPShortcutManager
2. Permissions required to run EVSPShortcutManager
3. EVSPShortcutManager syntax
4. EVSPShortcutManager examples
EVSVR
1. About EVSVR
  1. About the checkpointing facility in EVSVR
  2. Note on performing EVSVR operations on CIFS and NTFS partitions
2. Starting EVSVR
3. EVSVR commands
4. EVSVR application states
5. Creating an EVSVR operation file
6. Editing an EVSVR operation file in which you have enabled checkpointing
7. Running an EVSVR operation
8. About the EVSVR operation settings
9. Using the output from one EVSVR operation as input for another operation
  1. About EVSVR item list files
  2. EVSVR operations that support item list processing
10. Viewing the EVSVR output log file
11. Running EVSVR in interactive mode
12. Improving EVSVR performance when processing CAB collections
FSARunNow
1. About FSARunNow
2. Running FSARunNow
3. FSARunNow syntax
4. FSARunNow examples
FSAUndelete
1. About FSAUndelete
2. Running FSAUndelete
3. FSAUndelete syntax
4. FSAUndelete examples
FSAUtility
1. About FSAUtility
2. Running FSAUtility
3. About using FSAUtility with EMC Celerra/VNX placeholders
  1. Configuring which API call FSAUtility uses to identify Celerra/VNX placeholders
  2. Example FSAUtility.exe.config file settings
4. FSAUtility options
NTFS to Centera Migration
1. About NTFS to Centera Migration
2. Managing migrator jobs using NTFS to Centera Migration
3. Creating migrator jobs using NTFS to Centera Migration
4. Deleting active jobs using NTFS to Centera Migration
5. Deleting source files after migration using NTFS to Centera Migration
6. NTFS to Centera Migration log files
Permissions Browser
1. About Permissions Browser
2. Running Permissions Browser
3. About the information that Permissions Browser provides
Policy Manager (EVPM)
1. About Policy Manager
2. Policy Manager syntax
3. Saving a Policy Manager initialization file as a Unicode file
4. Policy Manager initialization file syntax
5. Sections and keynames in Policy Manager initialization file
6. Policy Manager initialization file examples
7. About using the Provisioning API to run Policy Manager scripts
ResetEVClient
1. About ResetEVClient
2. ResetEVClient syntax
Vault Store Usage Reporter
1. About Vault Store Usage Reporter
2. Starting Vault Store Usage Reporter
3. Setting up a shortcut link to Vault Store Usage Reporter
4. Understanding the usage summary from Vault Store Usage Reporter
5. Checking that the IIS authentication method is correctly set for Vault Store Usage Reporter

ExtractSavesets command

The ExtractSavesets command extracts one or more savesets from the following types of files:

EMC Centera data blob files
Enterprise Vault Storage Queue (.EVSQ) files

These types of files are called appended savesets files because they contain multiple savesets that are appended together.

Syntax

ExtractSavesets AppendedSavesetsFile [-o OutputFolder] [-n FileNameTemplate] [-f Offset -s Size]

Where the parameters are as follows:

*AppendedSavesetsFile*	Specifies the full path to the file that contains the savesets.
*OutputFolder*	Specifies the path to the folder in which to store the retrieved files and log file. By default, this is the `Reports\EVSVR` subfolder of the Enterprise Vault program folder (for example `C:\Program Files (x86)\Enterprise Vault`).
*FileNameTemplate*	Specifies the file naming convention to use for the extracted savesets. If you do not specify a file name template, EVSVR applies the name of the input file to the savesets, but without the path or extension. If you do not specify an offset and size, EVSVR extracts all the savesets and sequentially names them `FileNameTemplate_nnn.DVS`. If you do specify the size and offset, EVSVR extracts the size bytes starting from offset into one saveset file that is named `FileNameTemplate.DVS`.
*Offset*	Specifies the offset in bytes from the start of the input file from which to start extracting the required saveset. If you specify an offset parameter, you must also specify a size parameter.
*Size*	Specifies the size in bytes of the data to extract from the input file. If you specify a size parameter, you must also specify an offset parameter.

Example

In the following example, the two parameters specify the path to an EMC Centera data blob file and the folder in which to extract its contents:

es "C:\Centera Blobs\2RGPDMAIG8D51eAMOCBFS25BBK2G415357TU510G996D0BM2P833O.Blob126" -o c:\MyOutputFolder

If the output folder does not exist, ExtractSavesets creates it. All ExtractSavesets files are output to a time-stamped folder under this output folder, such as EVSVR_ExtractSavesets_20100715131545. So, in this example, the full output path is as follows:

C:\MyOutputFolder\EVSVR_ExtractSavesets_20100715131545\

The sample command does not include a -f parameter to specify the offset or a -s parameter to specify the size, so it extracts all the savesets in the blob file.

Expected outputs

Except where noted, ExtractSavesets 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 `EVSVR_ExtractSavesets_20100715131545.Log`. Always review the log file to determine how successful the operation was. The file shows any errors that occurred.
Extracted Savesets folder	This folder contains the files that ExtractSavesets has extracted from the input file. See Table: Contents of the Extracted Savesets folder.

Output

Description

Log

This is the log file. In the example above, its file name is EVSVR_ExtractSavesets_20100715131545.Log.

Always review the log file to determine how successful the operation was. The file shows any errors that occurred.

Extracted Savesets folder

This folder contains the files that ExtractSavesets has extracted from the input file. See Table: Contents of the Extracted Savesets folder.

Table: Contents of the Extracted Savesets folder

Output	Description
DVS	Given the specified input parameters, if the appended saveset file contains DVS data, the command extracts all the DVS files from it. The name of each DVS file has the form `AppendedSavesetName_IndexNumber.DVS`. For example: `2RGPDMAIG8D51eAMOCBFS25BBK2G415357TU510G996D0BM2P833O_001.DVS`
DocFile	This file is an uncompressed structured storage version of the above extracted DVS file. You can inspect its contents with a structured storage viewer. Sample file name: `2RGPDMAIG8D51eAMOCBFS25BBK2G415357TU510G996D0BM2P833O_001.DocFile`

Output

Description

DVS

Given the specified input parameters, if the appended saveset file contains DVS data, the command extracts all the DVS files from it. The name of each DVS file has the form AppendedSavesetName_IndexNumber.DVS. For example:

2RGPDMAIG8D51eAMOCBFS25BBK2G415357TU510G996D0BM2P833O_001.DVS

DocFile

This file is an uncompressed structured storage version of the above extracted DVS file. You can inspect its contents with a structured storage viewer. Sample file name:

2RGPDMAIG8D51eAMOCBFS25BBK2G415357TU510G996D0BM2P833O_001.DocFile

More Information

Note on reviewing the messages in the EVSVR log files