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 box

This dialog box lets you define the following:

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.

    Note:

    EVSVR processes all collections, where appropriate. The option to process a single collection is not available at this release.

  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 select Set Date Range and specify a date range in the Items archived from boxes.

    Note the following:

    • 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 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. This may be the case, for example, if you want to perform a daily Verify operation to validate the last week's archived items only.

    • When it performs an operation that scans a CIFS partition, EVSVR assumes that the original creation dates of the folders are maintained. If this is not the case because, for example, you use backup software that does not restore the original dates of the folders, date range selection may give unexpected results.

    Operation to perform

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

    Logfile

    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.

    • The name of the log file. If you check Auto Generate Filename, EVSVR uses the default file name, which is as follows:

      EVSVR_yyyymmddhhmmss.Log

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

      If the log file already exists, EVSVR appends the new information to it.

    Threads

    Specify the thread count for EVSVR operations that can benefit from using multithreading. The maximum is 16. You may want to try a thread count that is double the number of processors that the computer has.

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

    If you set the thread priority to High for the Repair operation RecreateMissingDBReferences, 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.

More Information

About the EVSVR operation settings