Applications Systems

Move a DPA repository on MySQL

This article explains how to move a DPA repository from one MySQL database to another.

First published date

10/22/2018 10:46 AM

Last published date

10/22/2018 10:46 AM

Overview

This article explains how to move a DPA repository from one MySQL database to another.

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

Product section

Database Performance Analyzer

Resolution

In DPA, click Stop All Monitors in the upper right.
Shut down DPA.
- Windows: Stop the IgnitePI service.
- Linux: Run shutdown.sh in the DPA installation directory. Ensure there are no crontab entries that will restart DPA.

Create a new empty database on the destination MySQL instance:

mysqladmin -u username --password="password" -h destination_hostname 
create databasename_name

Copy the database to the destination server:
```
mysqldump -u username --password="password" current_db_name | mysql 
-u destination_username --password="destination_password" -h hostname 
databasename_name
```
For more information, see the MySQL documentation (© 2018 Oracle Corporation and/or its affiliates, available at dev.mysql.com, obtained on November 21, 2018)
On the DPA server, open the repo.properties file in a text editor.
- Windows: This file is located at DPA_install_dir\iwc\tomcat\ignite_config\idc
- Linux: This file is located at DPA_home/iwc/tomcat/ignite_config/idc
Edit the values for the following lines to point to the new repository:
```
repo.user=
repo.databaseName=
repo.host=
repo.password=
repo.name=
```
Start DPA.
- Windows: Start the IgnitePI service.
- Linux: Run startup.sh in the DPA installation directory.
In DPA, make sure the server connects to the new MySQL repository database.
Review the status of the database monitors, and start or stop them accordingly.
Review the DPA log for errors.
Wait for 10 minutes, and drill down into each monitored database instance.
Make sure that you see data from the last 10 minutes for the database instances.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.