Best Practices for Enterprise Vault Backup
|Article:TECH172279|||||Created: 2011-10-20|||||Updated: 2014-02-12|||||Article URL http://www.symantec.com/docs/TECH172279|
This document features the recommended 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.
Three specific areas require a full backup: Vault Stores and Vault Store partitions, Index storage locations, and all related EV SQL databases.
|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|
|Enterprise Vault SQL Databases||Storage for the detailed information about the items stored in any archive|
Backups must include all EV SQL databases:
- Vault store database(s)
- Fingerprint database(s)
- EnterpriseVaultAudit (if applicable)
- FSA Reporting database (if applicable)
Note: The Vault Store, Index and database locations and size vary depending on the specifics of the site.
Support has created technical articles to assist with the implementation of a backup plan.
|Backing up Enterprise Vault: White Paper||TECH147148|
|Backing up Enterprise Vault: Medium Environment||DOC4933|
To prevent data loss or a database deadlock during a backup operation, backup mode must be enabled. Symantec's Backup Exec, NetBackup and other third party applications enable this option in two ways.
- PowerShell cmdlet
- Using the Vault Administrative Console (VAC)
PowerShell cmdlet: Transform-Backup.ps1
Manually using the VAC
Support has provided TECH74666 to illustrate creation process of a SQL Server Maintenance Plan. The article provides guidance on configuring Microsoft’s built-in backup tool.
Note: 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.
Note: 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 EV that items have been properly secured. This action can be simulated with the creation of trigger files. Reference TECH35610 for more information on the use and creation of trigger files
Article URL http://www.symantec.com/docs/TECH172279