Best Practices for Enterprise Vault Backup

Best Practices for Enterprise Vault Backup

Article: 100006827
Last Published: 2020-02-27
Ratings: 3 7
Product(s): Enterprise Vault


This document features a high level view of the best practices for backing up Enterprise Vault (EV). Specifically, the review of data locations, SQL databases, backup modes and commands, backup tools, and server maintenance plans.

EV stores business critical information, which is housed in many locations and is constantly changing. In a disaster recovery situation it is imperative that this information is readily available with a recent backup to ensure business continuity.

Note: Additional information is listed in the related articles section at the bottom of this solution.


This article does not contain the step-by-step set of instructions of an implementation backup plan. These instructions are located in the NetBackup for Enterprise Vault Administrator's Guide.

This article highlights the key items to consider when scheduling your backup routine.



Enterprise Vault Components:

The table below diagrams the specific areas that require a full backup: 

Enterprise Vault Component Description
Vault Stores and Vault Store partitions Locations of archived items stored by Enterprise Vault
Index Locations Collections of data obtained from within an archived item that can be used to find that archived item
Storage Queue Holding location for safety copies.
* Enterprise Vault SQL Databases Storage for the detailed information about the items stored in any archive

* Backups must include all Enterprise Vault SQL databases:

  • Vault store database(s)
  • Fingerprint database(s)
  • EnterpriseVaultDirectory
  • EnterpriseVaultMonitoring
  • EnterpriseVaultAudit (if applicable)
  • FSA Reporting database (if applicable)

Note: The Vault Store, Index, storage queue and database locations and size vary depending on the specifics of the site. 


Setting Backup Mode

To prevent data loss or a database deadlock during a backup operation, backup mode must be enabled.  Veritas's Backup Exec, NetBackup and other third party applications enable this option in two standard ways using the PowerShell cmdlet and Using the Vault Administrative Console (VAC).  


PowerShell cmdlet

  • Script Name: Transform-Backup.ps1
           Located in the Templates folder beneath the EV installation folder
  • Generates PowerShell backup mode commands
  • Designed to be used in the backup scripts to control backup mode
  • See Generating PowerShell backup commands for your environment for detailed configuration information


Manually using the VAC

  • Manual process sets backup mode on vault stores and index locations in the Enterprise Vault VAC
  • When the backup is complete, use the administration console to clear backup mode
  • See About Enterprise Vault backup mode for detailed configuration information 



Removal of safety copies using a trigger file

  • By default, Enterprise Vault determines that an item is backed up when the archive bit on the file is reset.
  • If after backup and with the Vault Store property is set to Remove Safety Copies: After backup, Enterprise Vault does not remove safety copies a trigger file must be created to complete the process.
  • Some backup programs do not support the use of or perform the proper reset of the archive bit.
  • The archive bit must be reset, as it notifies Enterprise Vault that items have been properly secured. This action can be simulated with the creation of trigger files.
  • Reference 100016637 or more information on the use and creation of trigger files



SQL server maintenance plan

  • 100022023 describes suggested steps for how an administrator can automate backups and perform recommended maintenance procedures. 
  • The article provides guidance on configuring Microsoft’s built-in backup tool The SQL Server Maintenance Plan.
  • The procedure is for Enterprise Vault (EV), Compliance Accelerator (CA), and Discovery Accelerator (DA) SQL databases using SQL Server maintenance plans.
  • The instructions are for EV environments where the application of a 'SQL Agent' is not used to perform a logical backup of the SQL Databases.  




Was this content helpful?