Enterprise Vault databases cannot be backed up by NetBackup Agent due to SQL server format in EVBackup.xml

book

Article ID: 100015955

calendar_today

Updated On:

Cause

By default, SQL Server connection library uses the TCP port 1433 to connect to a SQL server instance. When SQL server is running over a non-default port (1433), the port number must be specified in the connection string. For instance:

SQLServer,10000

The format above allows Enterprise Vault to connect to the default SQL server instance in a server called SQLServer using the TCP port 10000. This format is accepted by Enterprise Vault. However, NetBackup Agent for Enterprise Vault needs the following format to perform a Enterprise Vault databases backup:

SQLServerName\InstanceName,Port

Resolution

Starting with NetBackup 7.5.0.6, the following workaround can be applied:

  1. Determine the SQL instance name from SQL Management Studio.
  2. Follow https://www.veritas.com/docs/000028296, Step #5, and update the SQL server name from SQLServer,Port format to SQLServer\Instance,Port format.

    How to move the Enterprise Vault SQL databases
    https://www.veritas.com/docs/000028296
  3. Generate EVBackup.xml file running the following command: sc control EnterpriseVaultAdminservice 136

 

Issue/Introduction

When SQL Server is running over a non-default port, NetBackup Agent for Enterprise Vault cannot perform a Enterprise Vault databases backup correctly due to a SQL Server format in EVBackup.xml file.