1. Support
  2. Knowledge base
  3. 100001989

NetBackup Enterprise Vault (EV) Agent support for using an "SQL alias" or "DNS alias" for the Directory Database.

Article: 100001989
Last Published: 2021-08-26
Ratings: 0 0
Product(s): NetBackup & Alta Data Protection

Problem

NetBackup Enterprise Vault (EV) Agent support for using an "SQL alias" or "DNS alias" for the Directory Database.

Solution

Enterprise Vault (EV) provides a mechanism called "Change Directory SQL Server" for reconfiguration and disaster recovery purposes.  For details, see the Veritas Enterprise Vault Administrator's Guide.
Enterprise Vault™ Administrator's Guide (veritas.com)
 
In some environments, this mechanism has been used to permanently "alias" the host server of the directory database. While the practice is not documented as such, it is commonly referred to as a "SQL alias" or "DNS alias."
 
NetBackup did not support this configuration of the Directory database or any of the EV Databases in older releases. Support has been added starting with the 7.6.0.2 release - refer to the related article for more information.
 
Most typically, the backups would fail with a status 130 and messages similar to the following will be written to the NetBackup logs:
BPRESOLVER log on the EV server:
ERR - bedsEnterpriseVaultInit():DLE_FindByName() for 'EV-DIR::\\Enterprise Vault Resources' Failed! (0xE00084AF:The directory or file was not found, or could not be accessed.) 
BPFIS log on the backend SQL server where the directory database resides:
INF - Extended status = 130:1:Error attempting to gather metadata.
FTL - snapshot creation failed - Error attempting to gather metadata., status 130
FTL - snapshot creation failed, status 130
 
In order for NetBackup to function properly, the MS SQL Server hostname (and instance name if applicable) configured via "Change Directory SQL Server" must correctly match that of the actual computer name.
 
Please Note! Whilst this article is focusing on the EV Directory Database Server configured to use an Alias, it is possible to configure all EV Database Server(s) to use an Alias, therefore this article applies to any of the EV Databases.
 

 

Was this content helpful?

Article Languages