Best Practices for Enterprise Vault Backup

This article does not contain step-by-step set of instructions of an implementation backup plan.

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

• Enterprise Vault components
• Setting backup mode
• Removal of safety copies using a trigger file
• SQL Server Maintenance Plan

 

---

 

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
Index Snapshot Locations	Location configured for storing the snapshots of the index data of the Enterprise Vault Index Server. The Enterprise Vault Administrator may wish to make an independent backup of index snapshot repository or index snapshot location, so that a copy of its contents can be used to recreate the index repository to a point-in-time state later. The contents of index snapshot repository will be used to restore snapshots of index data for Elasticsearch indexes. Enterprise Vault recommends regular backing up of index snapshot repository or index snapshot location.
Storage Queue	Holding location for safety copies.
* Enterprise Vault SQL Databases	Storage for the detailed information about the items stored in any archive

Note: Enterprise Vault 14.2 uses Elasticsearch for indexing. Therefore, Enterprise Vault 14.2 onwards, the only reliable and supported way to back up the index data is by taking a snapshot. For more information, see:

• How to backup indexes in Enterprise Vault 14.2 and later 
• How to restore Elasticsearch index data in Enterprise Vault 14.2 and later

* 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.