How to migrate or move the middleware and Quest repository database to a new server? (4277495)

A new server is purchased and we would like to migrate / move the current middleware server agent and Quest Performance repository database to the new server. The Quest Performance repository database currently resides on the same server with the middleware server agent.

If the middleware server agent and repository database are on different servers, this KB article can also be used to apply to the specific migration.

How to migrate / move the middleware and Quest Performance repository database to a new server.

In the solution we will refer to two machines:

• OLD middleware machine, which is the existing middleware server.

• NEW middleware machine, which is the new middleware server.

1. Install new middleware agent on the NEW middleware machine

1. Verify that the installer matches the OS of the new MW server.
2. Run a new Middleware agent installation on the target middleware machine.
3. Once the installation is complete, verify QAM Launcher service is running in the Windows Services console.

2. Remove the HOST-INSTANCE folder for the agent from the OLD middleware machine.

1. From the Windows Services console of the OLD middleware server, stop the QAM Launcher.
2. Remove the 2 'host-instance' directories corresponding to the agent you are going to move.
   1. There is one in ..\agents\SC_MSSQL\7.0\ and one in ..\agents\SC_MSSQL\Data
3. Start the QAM Launcher on the OLD middleware server.

3. Remove the collector agent on the monitored host.

1. Unregister the service from a command prompt:

• • Open a command prompt
  • CD to <install_dir>agents/bin
  • Run quest_launcher.exe <port> -unregister (port is the port number such as 3566)
  • Exit command prompt

If the monitored host is a cluster, do the following:

• • Copy the quest_launcher.exe file from <install_dir>agents/bin directory on the active node to a <temp> directory on the passive node
  • Open a command prompt
  • CD to <temp> directory where quest_launcher.exe was placed
  • Run quest_launcher.exe <port> -unregister
  • Exit command prompt
  • Repeat step 3 for each passive node

4. Install SQL Server collector agent on monitored host

1. Run a new SQL Server collector agent installation (please be sure to use the correct binary installer 32-bit or 64-bit):

• • During the installation, specify the hostname of the new middleware 64-bit server.
  • Select No when asked to configure the Performance Repository database (it will be done later after the existing performance repository database is migrated to the new middleware server)

5. Post middleware server migration validation

1. Launch Performance Analysis Client GUI
2. Connect to the appropriate monitored instance
3. Verify Collect, & Middleware agents are up and running in Agent Administration
4. Verify that new data is collected

6. Migrate / Move Quest Performance Repository Database to new server

1. Watch the video at https://support.quest.com/performance-analysis-for-sql-server/kb/86655 to migrate the performance repository database to a new server.

7. Post Quest Performance Repository Database migration validation

1. Launch Performance Analysis Client GUI
2. Connect to the appropriate monitored instance
3. Verify Collect, Middleware, and Performance Repository agents are up and running in Agent Administration
4. Verify that all available data is loaded appropriately on History page