About Enterprise Vault directives and what data they back up
When you create a policy to back up Enterprise Vault data, you choose the directive based on the data that you want to back up. In addition, the data that is backed up also depends on the client(s) that you select in the policy. The following table identifies each of the available Enterprise Vault directives along with a brief summary of the data that is backed up when that particular directive is selected.
Veritas recommends that you create Enterprise Vault policies with the directives that do not back up the same Enterprise Vault data. For example, an Enterprise Vault backup policy with the EV_SITE directive can back up the same data as a backup policy with the EV_SERVER directive. In this case, running the Enterprise Vault backup policy that is configured with the EV_SERVER directive is not necessary.
Table: Enterprise Vault directives and what they back up shows the Enterprise Vault directives. In the following table a policy client has been specified and each directive applies to full, differential, and cumulative backups. In addition, Enterprise Vault supports multiple policy clients (except for the EV_VAULT_STORE_DB=, EV_OPEN_PARTITION=, EV_READY_PARTITIONS=, EV_CLOSED_PARTITIONS=, EV_FINGERPRINT_DB=, and EV_VAULT_STORE_DB= directives).
Table: Enterprise Vault directives and what they back up
Directive (backup selection) | Description |
|---|
EV_DIR_DB
| The directory database is an SQL database that contains configuration information. Use this directive to back up the directory database of the Enterprise Vault site that the policy client belongs to. The directory database does not need to be hosted on the policy client. This database is known as a site-level database. This directive supports multiple policy clients in the client list. You should add multiple clients when multiple Enterprise Vault sites have their own directory database. You cannot use this directive with the EV_INDEX_LOCATION= and the EV_OPEN_PARTITION= directives.
|
EV_MONITORING_DB | The monitoring database is an SQL database that is associated with the Enterprise Vault monitoring service. This database typically contains performance and trend information about Enterprise Vault activities. Use this directive to back up the monitoring database of the Enterprise Vault site that the policy client belongs to. The monitoring database does not need to be hosted on the policy client. This database is known as a site-level database. This directive supports multiple policy clients in the client list. You should add multiple clients when multiple Enterprise Vault sites have their own monitoring database.
|
EV_AUDIT_DB | The auditing database only exists if Enterprise Vault auditing is enabled. The
audit database contains audit records of various configurable Enterprise Vault
operations. Use this directive to back up the auditing database in the Enterprise Vault deployment if you have Audit enabled. This option is disabled by default. The auditing database does not need to be hosted on the policy client. This directive supports multiple policy clients in the client list. You should add multiple clients when multiple Enterprise Vault sites have their own auditing database.
|
EV_FSAREPORTING_DB | The FSA Reporting database only exists if FSA Reporting has been configured.
The FSA Reporting database contains a history of the active and the archived
files on the file servers. This data is used to track trends and as a summary of
the archived files and active files on file servers. Use this directive to back up the FSA Reporting database in the Enterprise Vault deployment if you have FSA Reporting enabled. This option is disabled by default. The FSA Reporting database does not need to be hosted on the policy client. This directive supports multiple policy clients in the client list. You should add multiple clients when multiple Enterprise Vault sites have their own FSA Reporting database.
|
EV_INDEX_LOCATION=Site name | Use this directive to back up all index locations in the Enterprise Vault site, that the Site name variable specifies. You can use any backup schedule with this directive. You cannot use this directive with the EV_DIR_DB directive. This directive does not support multiple policy clients in the client list. If Site name is not specified, the job fails.
|
EV_OPEN_PARTITION=Vault Store name | The open partition directive backs up the open partition
and Vault Store database of the Vault Store
that you specify when you define the Vault Store name.
The partition can be present on NTFS file system or NAS
devices. You can use any backup schedule with this directive. For open partitions: You cannot use this directive with the EV_DIR_DB directive. This directive does not support multiple policy clients in the client list. If Vault Store name is not specified, the job fails.
For the streamer-based open partitions, do not use this directive as the backup would succeed partially. Instead, use the EV_VAULT_STORE_DB directive. |
EV_CLOSED_PARTITIONS=Vault Store name | The closed partitions directive backs up any closed partitions
of the Vault Store
that you specify when you define the Vault Store name.
The partitions can be present on NTFS file system or NAS
devices. You can use any backup schedule with this directive. For closed partitions: This directive does not support multiple policy clients in the client list. If Vault Store name is not specified, the job fails.
Do not use this directive for streamer-based closed partitions. If some closed partitions are streamer-based, the job is completed, but the data is not backed up by NetBackup. If all close partitions are streamer-based the job fails. |
EV_READY_PARTITIONS=Vault Store name | The ready partitions directive backs up the ready partitions
of the Vault Store that you specify when you define the Vault Store name.
The partitions can be present on NTFS file system or NAS
devices. You can use any backup schedule with this directive. For ready partitions: This directive does not support multiple policy clients in the client list. If Vault Store name is not specified, the job fails.
Do not use this directive for the streamer-based ready partitions. If some ready partitions are streamer-based, the job is completed but the data is not backed up by NetBackup. If all ready partitions are streamer-based the job fails. |
EV_VAULT_STORE_DB=Vault Store name | The Enterprise Vault, vault store database is an SQL database that can contain metadata about the vault store and archived data. Use this directive to back up the vault store database that the Vault Store name variable specifies in the Enterprise Vault deployment. You can use any backup schedule with this directive. The following applies for this directive: The vault store databases can be hosted on a different system. This directive does not support multiple policy clients in the client list. If Vault Store name is not specified, the job fails. The vault store name is the vault store name and not the vault store database name.
|
EV_FINGERPRINT_DB=Vault Store Group name | The fingerprint database contains information about archived data in Vault
Store Partitions. Use this directive to back up the fingerprint database that is associated with the supplied Vault Store Group. The Enterprise Vault agent can discover multiple fingerprint databases when a Vault Store Group is configured to support multiple fingerprint databases. You can use any backup schedule with this directive. The following applies for this directive: The fingerprint database can be hosted on a different system. The job fails if the Vault Store group name is not specified. This directive does not support multiple policy clients in the client list.
|
