The Microsoft application agent
19.17 supports a direct update from any supported version to the latest version.
NOTE:
The same version of Microsoft application agent must be installed on each node in an AAG or FCI cluster that is registered to
PowerProtect Data Manager.
During an update from an earlier version, first update the
PowerProtect Data Manager to version
19.17 as needed and then update the Microsoft application agent on the Microsoft SQL Server host.
If a table-level restore was performed since the last reboot of the host, the Microsoft application agent requests a reboot during an uninstall operation. The Microsoft application agent installs and uses the EldoS CBFS driver for table-level restores. The EldoS CBFS driver is loaded during the table-level restore operation. Microsoft requires the driver to be unloaded before an uninstall operation.
Launch
emcmsappagent-19.17.0.0.exe. The installation wizard appears.
On the
Welcome Wizard page, select
I agree to the license term and agreements, and then click
Next.
By default, the
PowerProtect Data Manager option is selected and the IP address is displayed. If these components were installed in the previous version,
SSMS Plug-in and
ItemPoint Granular Recovery are also selected.
Whether the
PowerProtect Data Manager option was previously selected or you select the option during this update, you can change the firewall rule setting by the
Configure the Windows Firewall option. Select the option to enable the
PowerProtect Data Manager communications port by creating the Windows firewall rule that grants the agent service inbound and outbound access.
NOTE:
The Microsoft application agent requires a selected port on Microsoft SQL Server (selected from port ranges 7000 to 7009 and 7012 to 7020) and port 8443 on
PowerProtect Data Manager to be open bidirectionally. These ports enable communication between the Microsoft application agent and
PowerProtect Data Manager. If you do not select a port from the port ranges, the default port 7000 is used as the communications port.
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.
Click
Upgrade.
On the
CLR assembly deployment wizard page, perform the following steps:
NOTE:When you deploy the CLR assembly during the Microsoft application agent update, the deployment creates a Microsoft SQL Server login with the name ddbmaCLRExtLogin. The CLR procedures run under this account.
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.
To deploy the CLR assembly, select one of the following authentication options:
NOTE: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
In the
User name and
Password fields, respectively, type the username and password of the user who has the privileges to deploy the CLR assembly.
Click
Deploy.
Click
Install.
After the deployment is completed, click
Next.
On the
Complete the Setup page, click
Finish.
If the update of the Microsoft application agent fails, complete the following steps:
Save a copy of the existing
DPSAPPS folder.
Uninstall the Microsoft application agent from
Control Panel > Programs > Programs and Features.
Install the Microsoft application agent.
Replace the
DPSAPPS folder with the copy that was saved in step 1.
Data is not available for the Topic
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: <>()\