Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager Appliance 5.16.0.0 Microsoft SQL Server User Guide

Install the Microsoft application agent with the wizard

Learn how to install the Microsoft application agent with the installation wizard.

About this task

NOTE:

In Always On availability group (AAG) or cluster environments, install the Microsoft application agent on each node in the cluster.

Install the same version of the Microsoft application agent on each node in an AAG or FCI cluster that is registered to PowerProtect Data Manager Appliance.

Starting with Microsoft application agent 19.14, migration of the Microsoft application agent from an Application Direct configuration to a VM Direct configuration or the opposite way is not supported. During installation, if you try to migrate from either type of configuration to the other, an error message is displayed about an invalid data path selection.

Steps

  1. In the PowerProtect Data Manager Appliance UI:
    1. Click Settings icon, and then select Downloads from the System Settings menu.
    2. Under Microsoft SQL Server, select Download Agent.
      The Microsoft application agent download package msappagent1916_win_x64.zip is downloaded.
    3. Upload the package to the Microsoft SQL Server host on Windows.
    NOTE:To verify the authenticity and integrity of the downloaded package, follow the instructions in the PowerProtect Data Manager Appliance Security Configuration Guide.
  2. Open msappagent1916_win_x64.zip with WinZip.
  3. Use WinZip to extract the msappagent1916_win_x64.zip file.
  4. In the extracted folder, launch emcmsappagent-19.16.0.0.exe.
    The installation wizard appears.
  5. On the Welcome Wizard page, select I agree to the license term and agreements, and then click Next.
  6. On the Change Install Location page, perform one of the following tasks:
    • To install the Microsoft application agent in the default folder, leave the installation location as is.

      The default installation folder is C:\Program Files\DPSAPPS\MSAPPAGENT.

    • To specify a different installation location, perform the following steps:

      1. Click Change.
      2. In the dialog box that appears, specify the installation location.
      3. Click OK.

    To allow full access for local Administrators, the Microsoft application agent grants the appropriate permissions on the directories under the installation folder. To support self-service backups under Microsoft SQL Server service accounts that are not Administrators, the Microsoft application agent also performs the following tasks:

    • Automatically discovers the service accounts for all Microsoft SQL Server instances that are installed on the system.
    • Grants those service accounts the appropriate permissions on the directories under the installation folder.
    NOTE:When you run a change installation operation, the Microsoft application agent also performs the following tasks:
    • Automatically rediscovers the service accounts for all Microsoft SQL Server instances that are installed on the system.
    • Grants those service accounts the appropriate permissions on the directories under the installation folder.

    The Microsoft application agent performs these tasks to accommodate the new Microsoft SQL Server instances that may have been installed after the initial installation of the Microsoft application agent.

  7. Click Next.
  8. On the Configure Installation Options page, specify any of the following installation options, as required:
    • To integrate the Microsoft application agent with PowerProtect Data Manager Appliance for centralized or self-service Application Direct protection of Microsoft SQL Server data, select the following options, as required:
      • To install the Microsoft application agent software, select Application Direct in the Data Paths group box.

        NOTE:

        The Microsoft application agent supports only the Application Direct and VM Direct workflows.

        Ensure that the Microsoft SQL Server host was not previously registered to PowerProtect Data Manager Appliance with the VM Direct option or as part of a virtual machine application-aware protection policy.

        For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager Appliance with VM Direct during the Microsoft application agent installation, the protection type for that host may not be changed to Application Direct, even if the Microsoft application agent is uninstalled.

      • To install the SQL Server Management Studio (SSMS) plug-in user interface, select SSMS Plug-in.

        You can use the SSMS plug-in to perform self-service Microsoft SQL Server backup and restore operations.

      • To enable table-level restores, select ItemPoint Granular Recovery.

        This option installs ItemPoint for Microsoft SQL Server, which you can use to perform table-level restores.

      • Specify the PowerProtect Data Manager Appliance server details by performing the following steps:
        1. Select PowerProtect Data Manager Registration at the top of the group box.

          NOTE:If the File System agent is installed first and then you install the Microsoft application agent with the wizard, it is mandatory that you select the PowerProtect Data Manager Registration checkbox. You must also provide the PowerProtect Data Manager Appliance server hostname or IP address in the Appliance hostname or IP address field. These settings can prevent issues with the registration to PowerProtect Data Manager Appliance.
        2. To enable the PowerProtect Data Manager Appliance communications port that you select in the Port field, ensure that the Configure the Windows Firewall option is selected. This option is selected by default.

          When the Configure the Windows Firewall option is enabled, the installation creates the Windows firewall rule that allows inbound and outbound connections for the agent service process. Installation of the Microsoft application agent requires a selected port on Microsoft SQL Server (selected from port ranges 7000 to 7009 and 7012 to 7020) and the port 8443 on PowerProtect Data Manager Appliance to be open bidirectionally. These ports enable communication between the Microsoft application agent and PowerProtect Data Manager Appliance.

          NOTE:If the File System agent is already installed and firewall rules are configured, then the Configure the Windows Firewall option is selected by default but disabled for the Microsoft application agent. Configurable ports for Microsoft SQL Server provides more information.
        3. In the Appliance hostname or IP address field, type the hostname or IP address of the PowerProtect Data Manager Appliance server.

          If you specify a hostname or fully qualified domain name (FQDN) with an underscore (_) for the PowerProtect Data Manager Appliance server, then the communication is done by the system IP, if provided by the system on registration.

          NOTE:Changing the PowerProtect Data Manager Appliance server hostname or IP address registers all the installed application agents to the new PowerProtect Data Manager Appliance server.
        4. To select a preferred host address for communication, select Preferred application host address for communication and then an entry from the dropdown list.

          If the Microsoft application agent is configured to use the
          Application Direct data path, the preferred host address can be an IPv4 address, an IPv6 address, or a fully qualified domain name (FQDN).
            

          NOTE:Selecting an FQDN ensures continued communication between PowerProtect Data Manager Appliance and the application agent host when the IP address changes. Using an FQDN is recommended for DHCP environments and other environments where static IP addresses can change. If the preferred address is an FQDN, ensure that lookup is enabled in the PowerProtect Data Manager Appliance UI. If lookup is not enabled, the preferred address defaults to an IP address.
          If the Microsoft application agent is configured to use the VM Direct data path, the use of an FQDN is unsupported, and the preferred host address can only be an IPv4 address or an IPv6 address.
        5. Select Port and specify the port number from the supported port ranges 7000 to 7009 and 7012 to 7020. The specified port is used for communication between the Microsoft application agent and PowerProtect Data Manager Appliance.

          NOTE:If you do not specify a port number, the default port 7000 is used as the communications port. The agent service message bus uses the ports 7010 and 7011.
    • To install the VM Direct Engine onto a virtual machine that is not part of a protection policy, so as to recover application-aware virtual machine backups from a differential virtual machine, select the following options as required:

      NOTE:

      By default, when a Microsoft SQL Server virtual machine is added to a virtual machine application-aware protection policy in PowerProtect Data Manager Appliance, the Microsoft application agent and ItemPoint are silently installed on the protected virtual machine. Before you restore a VM Direct Engine backup to an alternate virtual machine that is not part of a protection policy, you must install the Microsoft application agent on the target virtual machine.

      As part of centralized restores, PowerProtect Data Manager Appliance also has centralized management for installing the Microsoft application agent on the virtual machine application-aware host that acts as a recovery-only host.

      • Select VM Direct in the Data Paths group box.

        NOTE:The PowerProtect Data Manager Appliance server and local network configuration options are disabled when you select the VM Direct option. PowerProtect Data Manager Appliance does not support the selection of a non-default communications port for Microsoft SQL Server application-aware (VM Direct) operations with Microsoft application agent.

        Ensure that the Microsoft SQL Server host was not previously registered to PowerProtect Data Manager Appliance with the Application Direct option. For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager Appliance with Application Direct during the Microsoft application agent installation, the protection type for that host may not be changed to VM Direct, even if the Microsoft application agent is uninstalled.

      • To install the SQL Server Management Studio plug-in user interface, select SSMS Plug-in.
      • To enable table-level restores, select ItemPoint Granular Recovery.

        This option installs ItemPoint for Microsoft SQL Server, which you can use to perform table-level restores.

  9. Click Install >.
  10. On the CLR assembly deployment wizard page, perform the following steps:
    1. Select or clear the Microsoft SQL Server instances on which you want to deploy the CLR assembly. By default, all the Microsoft SQL Server instances are selected.
      Deploying the CLR assembly enables you to run the T-SQL backup and restore scripts that use the CLR-integrated T-SQL functions.
    2. To deploy the CLR assembly, select one of the following authentication options:
      NOTE:

      When you deploy the CLR assembly during the Microsoft application agent installation, the deployment creates a Microsoft SQL Server login with the name ddbmaCLRExtLogin. The CLR procedures run under this account.

      When you change or repair an existing Microsoft application agent installation, the Microsoft application agent registers the CLR assembly with any new Microsoft SQL Server instances that were installed. The authentication option that is used is the one selected as follows with the initial installation.

      • Current Windows User
      • Use Windows Authentication
      • Use Database Authentication
    3. In the User name and Password fields respectively, type the username and the password of the user who has the privileges to deploy the CLR assembly.
    4. Click Deploy.
    5. Click Install.
    6. After the deployment is completed, click Next.
  11. On the Complete the Setup page, click Finish.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\