Veritas Enterprise Vault™ Backup and Recovery

Last Published:
Product(s): Enterprise Vault (12.1)
  1. About this guide
    1. Where to get more information about Enterprise Vault
      1.  
        Enterprise Vault training modules
  2. Introduction to Enterprise Vault backup and recovery
    1.  
      About backup and recovery
  3. Backing up Enterprise Vault
    1.  
      About Enterprise Vault backups
    2.  
      About Enterprise Vault backup mode
    3. Backup of Enterprise Vault data
      1.  
        Enterprise Vault system databases backup
      2.  
        Fingerprint databases backup
      3. Vault store partitions and vault store databases backup
        1.  
          Removal of Enterprise Vault safety copies after backup
      4.  
        Backing up index locations
    4. About backup mode cmdlets
      1.  
        Index location backup mode cmdlet syntax
      2.  
        Vault store backup mode cmdlet syntax
    5.  
      Generating PowerShell backup commands for your environment
    6.  
      Using PowerShell cmdlets in backup scripts
  4. Enterprise Vault recovery procedures
    1.  
      About using EVSVR as part of the recovery procedure
    2. Recovering Enterprise Vault using full system backups
      1.  
        Carrying out an environment recovery procedure
    3. Recovering Enterprise Vault using data-only backups
      1.  
        Recovery procedure 1: Installing software on the servers
      2.  
        Recovery procedure 2: Restoring Enterprise Vault system databases
      3.  
        Recovery procedure 3: Renaming servers
      4.  
        Recovery procedure 4: Copy or move the Enterprise Vault data files
      5.  
        Recovery procedure 5: Clearing the directory database entries
      6.  
        Recovery procedure 6: Recreating services and tasks on the first Directory service computer
      7.  
        Recovery procedure 7: Recreating services and tasks on Enterprise Vault servers
      8.  
        Recovery procedure 8: Checking the Web Access application settings
      9.  
        Recovery procedure 9: Checking registry entries
    4.  
      Recovery of an Enterprise Vault component
    5. Recovery of Enterprise Vault in a VCS cluster
      1.  
        Recovery scenario 1: One of the cluster nodes needs rebuilding
      2.  
        Recovery scenario 2: All the cluster nodes need rebuilding
    6. Recovery of Enterprise Vault in a Windows Server failover cluster
      1.  
        Recovery scenario 1: One of the cluster nodes needs rebuilding
      2.  
        Recovery scenario 2: All the cluster nodes need rebuilding

Recovery procedure 7: Recreating services and tasks on Enterprise Vault servers

If you are recovering all the Enterprise Vault servers that run a Directory service, for the first one you must use Recovery procedure 6.

See Recovery procedure 6: Recreating services and tasks on the first Directory service computer.

When you recover the subsequent servers including other servers that run a Directory service, use the procedure described in this section.

The Enterprise Vault Configuration wizard is able to detect missing services and tasks provided that the server name is identical to that in the original installation, or you have correctly followed Recovery procedure 3.

See Recovery procedure 3: Renaming servers.

To recreate services on other Enterprise Vault servers

  1. Make sure the server running the Directory service is available on the network and the Directory service is started.
  2. Make sure the Admin service is started on the local computer.
  3. Start the Enterprise Vault Configuration wizard on the server.
  4. When asked whether you want to create a directory or use an existing one, select No, use existing remote Vault Directory and enter the name of the server running the Directory service.
  5. Enter the password of the Vault Service account. This is necessary to recreate the Enterprise Vault services on the computer.
  6. The Enterprise Vault Configuration wizard recreates the Enterprise Vault services and tasks that used to run on the server and displays a message to indicate success.
  7. If the Enterprise Vault Configuration wizard does not display a success message, do not continue to run the wizard. Close the wizard and then do the following:

    • Check that all previous steps have been successful, repeat any missed steps, and then run the Enterprise Vault Configuration wizard again.

    • Create a String registry value called UseLanManNameForSCM under the following registry key:

      HKEY_LOCAL_MACHINE
       \SOFTWARE
        \Wow6432Node
         \KVS
          \Enterprise Vault
           \Admin
    • Give UseLanManNameForSCM a value of 1.

    • Run the Enterprise Vault Configuration wizard again

    • If you are sure you have followed all steps correctly and setting the registry key does also not help, contact your Enterprise Vault Support Representative for further assistance.

  8. Start all the Enterprise Vault services.

    The message queues should automatically be recreated on the new server. If the Storage service is configured to start multiple processes, it may stop during message queue creation. This is because of a conflict between the processes creating the queues. To fix the problem, restart the Storage service.

    If the Indexing service finds any inconsistency in the index metadata, it automatically synchronizes the metadata. You may see the following events:

    Event 41395 Index Volume metadata upgrade required
    Event 41372 Index Volume metadata synchronization started

    During the synchronization the Indexing service logs progress events every 10 minutes. At the end of the synchronization, one of the following events is logged:

    Event 41373 Index Volume metadata synchronization completed
    Event 41377 Index Volume metadata synchronization completed

    The index synchronization may take some time. For example, an Enterprise Vault recommended specification server takes approximately 10 minutes to process 5,000 index volumes.

    If any other index housekeeping is required there will be other progress messages every few minutes.