Avamar: Avamar SQL Plugin Installation and Configuration - Resolution Path


   Article Number:     500275                                   Article Version: 7     Article Type:    How To 




Avamar Plug-in for SQL,Avamar





The aim of this article is to offer a general guide of common problems reported during the installation and configuration of the SQL plugin with Avamar.   
    It will cover issues related to standalone servers, clusters, and AlwaysON Availability group.   
    For any other problems not listed in this KB, please search our knowledge article database for the resolution: Knowledgebase   






1) First of all, open the compatibility guide to verify that the current SQL version installed is supported.   
    Select the Avamar Server version on the left pane:   
    User-added image   
    In the second middle pane under Custom Reports scroll down to Applications, then select these options and click "Generate Report":   
    User-added image   
    Note: Support for SQL 2016 started on Avamar version 7.3.1 and later, however it is also supported  on 7.2 and 7.3 with a client hotfix: Please see KB 498934   

  •         498934 - Backup of SQL Server 2016 on Avamar 7.2 and 7.3     
    2) Verify that the SQL environment meets the installation requirements described in the Avamar for SQL Server User Guide: 7.1 , 7.2, 7.3, or 7.4.   
    NOTE: Search for the following string on the above guides  "Preparing to install the SQL Server plug-in"   
    3) Always make sure that the Avamar client and the SQL plugin version match.    
    Common SQL plugin installation issues:   
  •         456712 - Problem installing Avamar Plug-in for SQL "Installation does not begin: error received: “Microsoft.SqlServer.Smo.dll version does not match the latest SQL server installation found on the system."     
  •         465560 - Unable to install VDPA SQL agent, installation failed: "Register Agent: Cannot connect to VDP appliance".     
  •         499040 - .NET Framework 4.5 is supported for Avamar client releases v7.2 and v7.3.     
    NOTE: If none of the above articles helped and an installation log is requested by support, install the SQL plugin msi package via CLI on a command prompt:   
      msiexec.exe [/i][/x] <path_to_package> [/L{i|w|e|a|r|u|c|m|o|p|v|x+|!|*}][/log] <path_to_log>   
      msiexec.exe /i "C:\Avamar_SQL_plugin.msi" /L*V "C:\install.log"   
      This will create an installation log, named "install.log", with verbose output, under C volume.  More msiexec.exe parameters can be found here.    
    Common SQL plugin configuration issues:   
  •         No major issues have been reported for an standalone configuration. Please refer to the "common notes for all architectures" at the end of this article.     
  •         499434 - Cluster Setup fails with Overlapped I/O operation is in progress.     
  •         486182 - Avamar Cluster registration fails with "CreateClusterGroupNetworkResource returns failure".     
  •         456464 - Avamar: SQL Cluster registration fails when the cluster has two separate IPs, one for production network and one for backup network.     
  •         466163 - Unable to register Windows cluster due to "Backup" network.     
  •         419009 - Fix listening port on a windows cluster.     
  •         487312 - When running Avamar Cluster Wizard - option to configure SQL AlwaysON is grayed out, error: "av_cluster_config_wizard INFO<0000>: Query for SQL availability group failed with error: Index (zero based) must be greater than or equal to zero...".     
  •         472013 - Avamar unable to configure SQL AlwaysOn cluster option 'Configure a new cluster client for all nodes' is grey out.     
  •         471611 - SQL AlwaysOn cluster failing registration when no shared drives are available to use.     
    Common notes for all architectures:   
    Once the plugin has been installed, the Avamar administrator needs to check the following:   
  •         The account that Avamar will use to connect to the SQL server.     
      By default, Avamar will connect to the SQL server using the Windows NT AUTHORITY\SYSTEM account; however, a custom SQL account can be used as well.   
  •         Either of these accounts must have the "sysadmin" role set up at the server level, otherwise the backup won´t work:     
      1. In SQL Server Management Studio, expand the Security node and then the Logins node for the instance in the left pane.       
        2. Right-click the NT AUTHORITY\SYSTEM account and select Properties.       
        The Login Properties dialog box appears.       
        3. Select the Server Roles page from the list in the left pane.       
        4. In the right pane, select the checkbox next to the sysadmin user.       
        5. Click OK.
  •         If a SQL account is needed to run the backup, it can be configured in the dataset under "more options" -> "show advanced options" ->Authentication     
      User-added image     
  •         The installation must also meet the port requirements which is described in the Avamar Product Security guide: 7.1, 7.2, 7.3, 7.4.     
      NOTE: Search for the following string on the above guides "Port Requirements"   
  •         The user databases don´t have the autoclose feature enabled. Disable it by following this procedure or apply a Hotfix as per KB 489801.​     
  •         Make sure that the "TCP/P" and "Shared Memory" are enabled for each instance:     
      1) Open  SQL Server Configuration Manager.       
        2) Expand SQL Server Network Configuration  and click on Protocols for MSSQLSERVER (or any other named instance ).       
        3) Right click on TCP/IP and select Enable.       
        4) Right click on Shared Memory and select Enable.       
        5) Restart SQL Server services for the changes to take effect.
  •         ​​The correct version of the SQL Server Management Object is installed on the SQL server as per KB 333217.     
      If the SQL Database Engine is version 2012, then install SMO 2012.     
      NOTE: Other components on a higher or lower SQL version could be installed on the SQL server, but the SMO installed version should match the databases version.   
      Links to the different SMO versions: SMO 2008SMO 2008 R2SMO 2012SMO 2014 , SMO 2016   
      How to install SMO:   
  1.         Open the link to the SMO installation package.     
  3.         Click on "Install Instructions"     
  5.         Search for the string "SMO".     
  7.         Once the package has been located, read the "NOTES" and installed any other required packages if needed. Example of this NOTE:     
  •           Note: Microsoft SQL Server Management Objects requires - Microsoft SQL Server System CLR Types. This is available on this page.       
      The SMO installation does not require a server reboot.