How to Backup Enterprise Vault Elasticsearch Indexes using Backup Exec

Article: 100056006
Last Published: 2023-05-15
Ratings: 0 0
Product(s): Backup Exec

Description

How to Backup Enterprise Vault Elasticsearch Indexes using Backup Exec 22.1 and above.

With Enterprise Vault 14.2 and above the Elastic search Index cannot be backed up from the EVSITE selection container. 

Elascticsearch Index Backup

The following steps need to be taken to backup the Elasticsearch Indexes using Backup Exec 22.1.

  1. Create an Index Snapshot Location. Enterprise Vault administrator must configure the index snapshot location on the Enterprise Vault index servers. Complete the steps from the technote 100051446
  2. Once the steps in the above-mentioned document are completed, the Index Snapshot Location needs to be put in Backup Mode before taking the backup, so that no indexing happens during the backup and consistency is maintained. Run below command on the Index servers Set-EVIndexSnapshotLocationBackupMode -SiteId “18F00EB8DCAE07D49B567698975CE32E91d10000evserver” , Where SiteId is the Entry ID of the Enterprise Vault site.
  3. Open Backup Exec Console and from the "Servers" tab select or add the Enterprise Vault Index server container. Create new backup job and from file system selections select the path for the "Index Snapshot location" created in  point 1 above. Schedule\Run this backup job to backup the contents of the Index location.
  4. Once the backup is complete, remove the Index Snapshot Location out of Backup Mode by running the below command, Clear-EVIndexSnapshotLocationBackupMode -SiteId “18F00EB8DCAE07D49B567698975CE32E91d10000evserver”, Where SiteId is the Entry ID of the Enterprise Vault site.

 

Elascticsearch Index Restore

The following steps need to be performed to restore Elasticsearch Indexes.

  1. The Enterprise vault Administrator needs to configure the Index Snapshot location as per 100051446
  2. Check if the path of the Index snapshot location is same as the one backed up or different using the command Get-EVIndexSnapshotLocation -OnlyActive
  3. If a new location is used, then it must be set using command Set-EVIndexSnapshotLocation and restart the indexing service on the server.
  4. Put the Index Snapshot location in Backup Mode before the restore so that no indexing happens during the restore and consistency is maintained. Run the command on the Index server, Set-EVIndexSnapshotLocationBackupMode -SiteId  “18F00EB8DCAE07D49B567698975CE32E91d10000evserver”, where SiteId is the Entry ID of the Enterprise Vault site.
  5. Create a File-Level restore from the backup set of the Index Snapshot Location. Restore the snapshot to the original location or redirect location option should be used if the path was changed.
  6. Once the restore is complete, then run command Restore-EVIndexSnapshot on the Index server.
  7. Clear the Backup Mode of the Index snapshot location once the restore process is complete using the command, Clear-EVIndexSnapshotLocationBackupMode -SiteId “18F00EB8DCAE07D49B567698975CE32E91d10000evserver”, Where SiteId is the Entry ID of the Enterprise Vault site.

Note: For more information on restoring the Elasticsearch Indexes in case Disaster Recovery scenario please refer this technote 100051838

 

Upgrade Scenarios:

If Enterprise Vault is upgraded to a version greater than or equal to 14.2, ensure that a backup of both earlier Velocity Indexes and newly introduced Elasticsearch Indexes is taken.

Velocity indexes can be backed up and restored from the EVSITE selections, while Elastic Search Indexes need to back up and restored as per the steps listed in this document.

Was this content helpful?