Error Message

After altering the location of the EnterpriseVaultDirectory or EnterpriseVaultAudit database(See Related Articles), the EVBackup.xml will continue to show the EnterpriseVaultDirectory Database location for both components.

Example:

The EVBackup.xml is designed to provide a list of EV resources for the EV Backup Agent to backup. Enterprise Vault utilizes the following Registry value to determine the SQL instance for the EnterpriseVaultDirectory as well as the EnterpriseVaultAudit when building the EVBackup.xml.

32-bit
HKLM\Software\KVS\Enterprise Vault\Directory\DirectoryService\SQLServer Name

64-bit
HKLM\Software\Wow6432Node\KVS\Enterprise Vault\Directory\DirectoryService\SQLServer Name

Prior to Enterprise Vault 10.0.4, there was not an explicit reference to the Audit database location.  This discrepancy will cause the EVBackup.xml to systematically reference the same SQL Instance for both database components, regardless if these databases reside on separate SQL Instances.
 

Below steps can be followed to workaround this issue:

1. After the EVBackup.XML is generated, open EVBackup.xml within a text editor.
2. Locate the DataRepository Component="Audit" value.
3. Manually edit the SQLServer value to match the alternate location of the EnterpriseVaultAudit database.
4. Save and close the file.
5. Set EVBackup.xml to Read-only so that this file is not modified systematically.
    

Note: Placing the EVBackup.xml in Read-Only will stop the file from being systematically modified.  If EV resources are added or changed, the EVBackup.xml must be set back to a read-write state in order for the changes to take effect (Ex. When creating/removing a new Vault Store). Once environmental changes are updated within the new EVBackup.xml, the location of the Audit DataRepository must be updated manually to match the valid location and the file be placed back into Read-Only mode.

 

This issue has been addressed as part of the following release:

Enterprise Vault 10.0.4 Release
 

The following are new documented instructions for the Audit database move operation:

1. Move the audit database to the new SQL Server.
2. On the Enterprise Vault server, use the ODBC Data Source Administrator to select the new SQL Server on the EVAudit ODBC data source.
3. Test the data source within the ODBC Data Source Administrator.

By following these steps, the following registry key is updated:

HKLM\Software\Wow6432Node\ODBC\ODBC.INI\EVAudit

KeyValueName: Server

This registry key is used when populating the EVbackup.xml data.

Note: If the above registry key is missing, Enterprise Vault will default to use the same SQL server as where the EnterpriseVaultDirectory database is located.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

 

When enabling Enterprise Vault (EV) Auditing, the EnterpriseVaultAudit database will reside on the same SQL Instance as the EnterpriseVaultDirectory database. It is this location which the EVBackup.xml utilizes for the location of both databases. If the EnterpriseVaultDirectory and EnterpriseVaultAudit databases reside on different SQL Instances, the EVBackup.xml will utilize the EnterpriseVaultDirectory database location for both database locations. This discrepancy will cause a backup failure of the Audit database when using the Veritas Backup Exec or Net Backup EV Agent.

ETrack: 2863351