DPA - difficulty monitoring DPA repository

robert777

We have our DPA repository running on the same MS SQL servers as our SolarWinds database.

But... they run in separate SQL Instances - instances SOLARWINDSINSTANCE and DPAINSTANCE.

Again, two instances on the same servers.

Servers are set up as Always On Failover Clusters. Each AG (Availability Group) has its own 'listener'

SOLARWINDSINSTANCE = SWLISTENER

DPAINSTANCE = DPALISTENER

I have the SolarWinds instance monitored in DPA and its working great.

Trying to add the DPA instance. When attempting to register the DPALISTENER DPA returns a message about "instance is already monitored".

However, I can't find the DPA instance in the DPA console.

Can anyone in the community provide some insight into what needs done to successfully monitor the DPA SQL instance in DPA?

Thank you!

Find more posts tagged with

dpa

Accepted answers

Lofstrand

Hi, the recommendation is to NOT monitor the DPA Repository instance with DPA. Not monitor itself.
SQL Sentry on the other hand is better on that.

See this page for example, DPA 2025.2 system requirements

All comments

danglenn

I haven't experienced this issue as I don't believe we have any servers using more than one SQL instance. However, I'm wondering if you tried registering the server using only server name and port number as opposed to the instance name?

Or used servername\instancename? Or if both failed for you.

jaminsql

We had some instances where the duplicate monitoring check wasn't working quite as we would want. When I have seen it detect a duplicate that wasn't in the past it was because of some issue with VM's that were cloned.

If you are sure there isn't an instance in DPA for this now one work around to disable the check and is to uncomment the following line from DPA's system.properties file and restart the DPA service.

# SUPPORT EASILY REGISTERING SINGLE DATABASE MULTIPLE TIMES
#com.confio.idc.wizard.allowDuplicateDatabaseRegistration=true

This allows you to by pass the check you can also send a support case with logs and we might be able to find why you are getting the block when it seems you should not.

Lofstrand

Hi, the recommendation is to NOT monitor the DPA Repository instance with DPA. Not monitor itself.
SQL Sentry on the other hand is better on that.

See this page for example, DPA 2025.2 system requirements