Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Database Performance Analyzer (DPA) > Move a DPA repository on SQL Server

Move a DPA repository on SQL Server

Updated March 11th, 2016 

Overview

This article provides brief information and steps to move a DPA repository on a SQL Server. 

SolarWinds DPA (formerly Confio Ignite) can utilize SQL Server for the DPA Repository. (To find the supported SQL Server versions, see the system requirements in the DPA help for your version of DPA.) This article provides instructions for moving a DPA repository from one SQL Server instance to another.

If you need to move a MySQL or Oracle repository, see the following:

Environment

  • All versions of DPA

Steps

This article assumes that the target SQL Server instance is already created.  Remote Connections must be enabled to allow TCP/IP and/or Named Pipe connections.

  1. In DPA, click Stop All Monitors in the upper right to stop monitors on the current SQL Server repository.

    2015-10-06_16-40-12.png

  2. On the server, shut down the Ignite PI Server service.
  3. In SQL Server Enterprise Manager, make a backup of the repository database.  Right-click the DPA repository database, and select Tasks > Back Up.

    sql_kb2.png

  4. Fill out the backup page with the database name and select Full as the Backup type. Add a location and file name for the backup.

    2015-10-06_16-57-37.png

  5. Copy the backup file to the computer where the target SQL Server instance resides.
  6. In SQL Server Management Studio on the target instance, right-click the Databases menu and choose Restore Database.
  7. Enter the name of the database that was backed up in the To Database field.
  8. Choose the From device option and add the location and file name of the backup file.
  9. Select the Restore check box, and click OK.

    movingsqlimg4.jpg

  10. Create the DPA internal user by choosing Security > Logins > Right-Click > New Login.

    movingsqlimg5.jpg

  11. Choose the Server Roles page and give the new DPA user the same security privileges as the previous DPA user.

    sql_privs.jpg

  12. On the User Mapping page, map the Repository Database to the DPA user. Give the new DPA user the same Database roles as the DPA user had in the previous repository.

    sql_user_map.jpg

  13. Test connectivity by remotely connecting to the Repository Connection User from SQL Server Management Studio.
  14. Open the repo.properties file on the DPA server with a text editor, and change the connection information.
    1. Open the repo.properties file in a text editor. The file is located in the following folder:

      DPA_home\iwc\tomcat\ignite_config\idc

    2. Update the following values with the new repository information.

      If you have kept the same port, database name, repository connection user, and password information, you will not need to edit those fields.

      repo.serviceName=
      repo.port=
      repo.user=
      repo.databaseType=SQL Server
      repo.guid=
      repo.created=
      repo.databaseName=
      repo.host=
      repo.password=
      repo.name=
      
  15. Start the Ignite PI Server service.
  16. Ensure that all monitors start in DPA.

Troubleshooting

To investigate connectivity issues to the new server, review the idc.log and idc-errors.log files for further information. If on the new server you are getting invalid user name and password for a windows account and all test seem that the user should work such as connecting in management studio from the DPA server. Try adding this property to the repo.properties file and restart the Ignite PI service. 

repo.jdbcDriverProperties=useNTLMv2\=true

To report any other issues, open a technical support ticket at http://www.solarwinds.com/support/ticket/. In preparation for your support ticket, zip up the logs directory, usually found in the following location:

DPA_home\iwc\tomcat\logs

Last modified
12:36, 13 Apr 2017

Tags

Classifications

Public