How to use a trigger file with Enterprise Vault in a Windows Server Cluster

Article: 100003500
Last Published: 2021-09-27
Ratings: 1 0
Product(s): Enterprise Vault

Problem

How to use the IgnoreArchiveBitTrigger.txt file with Enterprise Vault in a Windows Server Cluster

Solution

To turn an item into a shortcut, the StorageFileWatch process checks the archive bit on the saveset (.dvs) files. However, some hardware and software platforms do not set this bit. Using the IgnoreArchiveBitTrigger.txt file will allow the items to be secured and changed from pending to shortcuts.

For information and steps to implement the IgnoreArchiveBitTrigger.txt file please refer to the following document:
 
How to use a trigger file for devices that do not support the Archive bit
 

For an Enterprise Vault installation in a Windows Server Cluster configuration, the root of the partition cannot be referenced as a local drive in the pre and post scripts. Instead, the cluster partition share name can be used to create the trigger file. In order to determine the share name for the EV Vault Store partitions, perform the following steps from the Failover Cluster Manager in a Windows Server Cluster:

  1. Open Failover Cluster Manager.
  2. Expand the cluster name.
  3. Expand Services and applications.
  4. Click on the Enterprise Vault service. In the right pane is the summary of the EV service. This service contains the Enterprise Vault cluster resources and Shared Folders. When Enterprise Vault creates a new partition, it creates a new shared folder with the words EVPartition at the beginning of the share name. Shared Folders are located at the bottom of the Summary page.

    Windows Server 2008 Failover Cluster Manager
     
  5. Do right click and click on Properties of the shared folder.

    Enterprise Vault partition properties Windows Server 2008 Cluster
     
  6. Notice the Share path in the Properties window. This path needs to be used in the pre and post scripts to create and delete the IgnoreArchiveBitTrigger.txt file. For example:

    Pre backup script:

    del > "\\EVServer\EVPartition01ce46760c5a1ac0$\ignorearchivebittrigger.txt"
    del > "\\EVServer\EVPartition01cf5e3cc0cfdb50$\ignorearchivebittrigger.txt"
    del > "\\EVServer\EVPartition01cf5e3cf36fc1b0$\ignorearchivebittrigger.txt"

    Post backup script:

    ECHO > "\\EVServer\EVPartition01ce46760c5a1ac0$\ignorearchivebittrigger.txt"
    ECHO > "\\EVServer\EVPartition01cf5e3cc0cfdb50$\ignorearchivebittrigger.txt"
    ECHO > "\\EVServer\EVPartition01cf5e3cf36fc1b0$\ignorearchivebittrigger.txt"

This will also work for N+1 Cluster Configuration. Follow the steps described above with the next Cluster Service and add the Enterprise Vault partition share path to the pre and post script.

 

Was this content helpful?