Database Management
Deploy or Move DPA Application Server to Microsoft Azure
SolarWinds Database Performance Analyzer (DPA) can be deployed in Microsoft Azure. If you are moving an existing DPA application/front-end server to Azure, the recommended approach is to deploy a new DPA server in Azure instead of relying on Azure Migrate as a DPA-specific migration tool.
First published date
Last published date
Overview
Use this article if you want to:
-
Deploy a new DPA server in Azure, or
-
Move the DPA application server to Azure while preserving your existing DPA repository and configuration.
This article focuses on moving only the DPA application tier. It is not a procedure for moving the DPA repository database.
Product section
Resolution
Recommendation
For Azure, the recommended SolarWinds approach is:
-
Create a new Azure virtual machine for DPA.
-
Install or deploy DPA on that Azure VM.
-
If you want to preserve the current DPA setup, move the DPA application configuration to the new Azure server using the supported server-move process.
Before you begin
Before starting, confirm whether your goal is one of the following:
Option 1: New Azure deployment
Choose this option if you want a fresh DPA deployment in Azure.
Option 2: Move an existing DPA application server to Azure
Choose this option if you want to keep using your existing DPA repository and carry over your current DPA application configuration to a new Azure-based DPA server.
If you are also upgrading DPA to a different version during the move, follow the version-specific upgrade guidance for that process as well.
Option 1: Create a new DPA server in Azure
SolarWinds provides a DPA image in the Microsoft Azure Marketplace. The Azure Marketplace deployment creates a virtual machine that contains a DPA server on Windows and a built-in Microsoft SQL Server instance configured as the DPA repository.
To deploy DPA from the Azure Marketplace:
-
Log in to the Azure Marketplace.
-
Search for SolarWinds, select Database Performance Analyzer, and click Create.
-
Complete the VM creation wizard, including the basic settings, VM size, optional settings, summary review, and purchase steps.
-
After the VM is created, open the VM in Azure, copy the Public IP address, and open it in a browser.
-
Accept the EULA, create a DPA password, select a time zone, and complete the DPA setup.
-
Register a monitored database instance and begin using DPA.
By default, the Azure Marketplace VM allows inbound HTTP and HTTPS traffic, and DPA is available on standard ports 80 and 443.
Option 2: Move an existing DPA application server to Azure and preserve the current setup
If you want to preserve the current DPA application setup, first deploy or install DPA on the new Azure VM and then follow the supported server-move process.
The process is:
-
Install DPA on the new Azure server.
-
Deactivate the DPA licenses on the old server.
-
Stop DPA on the old server.
-
Copy the ignite_config files/folders to the new Azure server, excluding cat.txt and java_loc.txt.
-
Verify the contents of repo.properties so the new DPA application server can still connect to the existing repository database.
-
Start DPA on the new Azure server and reactivate the licenses there.
Important notes
-
If your goal is only to deploy DPA in Azure as a new environment, use the Azure Marketplace deployment procedure.
-
If your goal is to preserve your current DPA setup, deploy the new Azure VM first and then use the supported DPA server-move process.
-
If the DPA application server and repository database are on separate servers, verify repo.properties carefully before starting DPA on the new Azure server.
-
If you also need to move the DPA repository database, use the repository-migration guidance instead of this article.