Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Virtualization Manager (VMAN) > Move Hyper9 data

Move Hyper9 data

You can migrate existing Hyper9 Virtualization Manager data between instances of the product installed on different systems.


The version of Hyper9 Virtualization Manager on the destination system must be the same or higher than the version on the original system.

Settings are not migrated

This procedure will not migrate custom settings from the original system. Custom settings include such settings as Active Directory integration and custom logs, among others. You must manually copy custom settings to the destination system:

On Windows systems, custom settings reside in Hyper9\Server\conf

On the appliance, customs settings reside in /var/hyper9/conf

Migrating data from an appliance to a Windows system

  1. Install the latest version of SolarWinds Virtualization Manager on the destination Windows system.
  2. Stop the Hyper9 service on the Windows system.
    1. Open the Windows Services list and then stop the Hyper9 service.
    2. Change the Hyper9 service from Automatic to Disabled.
  3. Open the database on the destination system for network access.
    1. Open the Windows Services list and stop the Hyper9DB service.
    2. Append the following line to Hyper9\DB\data\pg_hba.conf
      host all all trust
    3. Restart the Hyper9DB service.
  4. Stop the Hyper9 service on the appliance.
    1. Log on with an SSH client to the appliance operating system as the hyper9 user:
      User Name: hyper9
      Password: ****** <-- contact Michael Nels or Scott Carter. Do not give this password to the customer. Use GoToMeeting or similar remote control software to enter the password yourself.
    2. Enter the command: sudo service tomcat6 stop
  5. Export the postgres database on the appliance to a file.
    1. If you want to export the entire database, enter the command:
      /usr/bin/pg_dump -F c -v -U h9pgsu hyper9db >h9.pgdmp
    2. If you want to export everything except performance data, enter the command:
      /usr/bin/pg_dump -F c -v -T sample_point -U h9pgsu hyper9db >h9.pgdmp
  6. Enter the command: /usr/bin/pg_restore -c -v -h -U h9pgsu -d hyper9db <h9.pgdmp/> where is the host name or IP address of the destination server.
  7. On the Windows server, remove the following line from Hyper9\DB\data\pg_hba.conf and then restart the Hyper9DB service:
    host all all trust
  8. Start the Hyper9 services and set them to start automatically.
    1. Open the Windows Services list and then start the Hyper9 service.
    2. Change the Hyper9 service from Disabled to Automatic.

Migrating data from one appliance to another

(in progress)

Migrating data from a Windows system to an Appliance

(in progress)

Last modified