Workaround

If a port number is required for the SQL server connection, and has been configured in EV, then the following should be performed to ensure the EVBackup.xml file contains the correct SQLServer entry.  This will allow the backup agent to read the name properly so that the backup does not fail on the communication to the SQL server. 

1.  Locate the EVBackup.xml file.  Located in the <Install_path>\Enterprise Vault\Reports folder on the EV server by default. 

2.  Open the file in a text editor and modify ALL SQLServer values so that they do not include the port number. 

Example:

 <DataRepository Component="Directory" Type="SQLDatabase" SQLServer="evsql\inst1,1458" DatabaseName="EnterpriseVaultDirectory" />

should be

 <DataRepository Component="Directory" Type="SQLDatabase" SQLServer="evsql\inst1" DatabaseName="EnterpriseVaultDirectory" />

3.  Save the file. 

4.  Right-click the file and choose Properties.

5.  On the General tab select the Read-only option and click OK to save the changes. 

Note:  If there are changes to the EV environment, a new vault store or index location added, then the EVBackup.xml must be updated using the following procedures.

1.  Rename the EVBackup.xml file to EVBackup.xml.old in the <Install_path>\Enterprise Vault\Reports folder. 

2.  Run the following command from a command prompt on the EV server to recreate the EVBackup.xml file with the additional information. 

3.  Repeat steps 1 - 5 above to ensure the SQLServer entry is correct in the newly created file. 

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see http://www.symantec.com .

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.