Creating an EVSVR operation file

Article:HOWTO57227  |  Created: 2011-08-01  |  Updated: 2013-07-12  |  Article URL
Article Type
How To


Creating an EVSVR operation file

You must create an operation file before you can perform an EVSVR operation. An operation file is an XML file that defines the actions that EVSVR is to perform, and on what data set.

You create an operation file by selecting the required options from the EVSVR Operations dialog box.

Figure: The EVSVR Operations dialog box

The EVSVR Operations dialog boxfirst graphic = out10; second graphic = new10

This dialog box lets you define the following:

  • The storage data and Directory data to process. EVSVR processes the data that is associated with one of the following:

    • All the partitions in all the vault stores in all the vault store groups in the Enterprise Vault site.

    • All the partitions in all the vault stores in a single vault store group.

    • All the partitions in a single vault store.

    • A single partition.

  • A specific archive to process. This applies only when EVSVR processes vault store databases or the archive information in the Directory database.

  • The date range of archived items to process.

  • The operation to perform.

  • The location for the output log file. The log file contains the results of the operation.

  • The number of threads to use, and the priority.


Depending on the operation that you choose to perform, some of these options may not be available.

To create an operation file

  1. At the EVSVR> prompt, type edit to open the EVSVR Operations dialog box.

    Note the following:

    • Operations XML File shows the name of the current operation file.

    • Site shows the name of the Enterprise Vault site for which to process the data. This is the site to which the Enterprise Vault server belongs. You cannot change the site.

  2. Specify the storage data that you want to process. By default, the operation file specifies that EVSVR is to process the data for all partitions in all vault stores in all vault store groups in the Enterprise Vault site. However, you can minimize the amount of data that you process as follows:

    • To process a single vault store group, uncheck Process All Vault Store Groups and then select the required group.

    • To process a single vault store, uncheck Process All Vault Stores and then select the required vault store.

    • To process a single partition, uncheck Process All Partitions and then select the required partition.

  3. Select the required values for the other settings, as follows:

    Process All Archives

    By default, EVSVR processes all the archives in the selected storage data set. To select an individual archive, uncheck Process All Archives and then select an archive.

    If there are a large number of archives, the dialog box displays a form so that you can filter by archive name.

    Date Range To Process

    Do one of the following:

    • Use the default setting, which does not impose a date range.

    • Select a time unit in the Unit box, and then specify the number of units in the Units box. For example, if you select Hour and 2, EVSVR processes the items that were archived in the two hours before the time that you start the EVSVR operation.

    • Select Use date range in the Unit box, and then check Set Date Range and specify a date range in the Items Archived From boxes.

      When you set a date range, the option Trust CIFS Partition Created Dates becomes available. For operations that scan CIFS partitions, this option can increase the speed with which EVSVR scans the partitions. However, you must be confident that all the folders and files that you want to scan have accurate creation dates, because these dates play an important part in helping EVSVR to determine when certain, older items were archived.

      • For each saveset (.dvs) file that Enterprise Vault 2007 or earlier has made, EVSVR uses the creation date to determine the date of the first archived item in the file. The last-modified date of the saveset file gives EVSVR the date of the last archived item that Enterprise Vault has added to the file as a sharer.

        The creation dates of saveset files may have changed if you have copied or moved them while restoring the partition from backup. On the other hand, if you trust the creation dates, and they fall outside the date range that you specify in EVSVR, then you can safely omit the files from the scan and so run it more quickly.

      • For each saveset file that Enterprise Vault 8.0 or later has made, EVSVR establishes the archive date by looking at both the last-modified date of the file and the date in its folder path. These dates are preserved during backup and restore operations, so they provide a more robust way to determine each item's archive date.

      Some EVSVR operations scan database records rather than the files in vault store partitions. For example, this is true of the ArchiveObjects Verify operation and DatabaseLinkages Verify operation. These operations ignore the Trust CIFS Partition Created Dates setting.


    Whether you choose a date range depends on the severity of the issues that you want to address. If you want to repair a substantial number of items as part of a recovery procedure, it is important not to set a date range. This allows EVSVR to repair as many items as possible. On the other hand, setting a date range is desirable if you want to process a handful of items or a known range of items.

    For example, suppose that a Repair operation has failed to repair a number of items. By repeating the operation against a date range that includes all the failed items, you may be able to identify the cause of the problem quickly. If you were to repeat the operation without specifying a date range, it could take days to complete.

    For a non-critical operation, it is usually desirable to choose a small date range - especially if you select a data set with a large number of archived items. For example, this may be the case if you want to perform a daily Verify operation to validate the last week's archived items only.

    Operation To Perform

    Select an operation type (Report, Verify, or Repair), and then set the required options.

    See About the EVSVR operation settings

    Log And Checkpoint Files

    Specify the following:

    • The folder in which to save the output log file. By default, EVSVR saves the file in the Reports\EVSVR subfolder of the Enterprise Vault program folder. If the log file already exists, EVSVR appends the new information to it.

    • The name of the log file and, if you enable checkpointing, the checkpoint file. If you check Auto Generate Filenames, EVSVR uses the default file name, which is as follows:


      Where yyyymmddhhmmss specifies the date and time at which EVSVR created the log file.

      If you enable checkpointing, EVSVR stores the checkpoint information in an XML file that is in the same folder as the log file. The name of the checkpoint file matches that of the log file but includes the suffix _Checkpoint. For example, if you set the log file name to EVSVR_Logfile.log, the corresponding checkpoint file has the name EVSVR_Logfile_Checkpoint.xml.


    Specify the number of threads to use for the EVSVR operation. The maximum is 16.

    All the Verify and Repair operations can benefit from using multiple threads, but this is particularly the case with the DatabaseReferences Repair operation. Most Report operations always run with one thread only, even if you request more.

    Specify the thread priority as Normal, Low, or High.

    If you set the thread priority to High for the Repair operation DatabaseReferences, EVSVR automatically resets the priority level to Normal. This is designed to stop potential problems with resource scheduling and thread contention. Although intermittent, these problems can lead to errors when EVSVR tries to repair certain database references.

  4. Click one of the following to save the specified values in an operation file:

    • Save. Saves the selected settings and their values in an operation file. If you previously saved the file, EVSVR overwrites the file. Otherwise, EVSVR prompts you for a file name.

    • Save As. Saves the selected parameters and their values in an operation file. EVSVR prompts you for a file name.

  5. After you have defined the operation, click one of the following to exit from edit mode and return to the EVSVR> prompt:

    • OK. Exits and loads the last saved operation file. Any changes that you have made since your last save are lost.

    • Cancel. Exits without loading an operation file. Any changes that you have made since your last save are lost.

See Editing an EVSVR operation file in which you have enabled checkpointing

See Running an EVSVR operation

See About EVSVR

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices