Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Perform backups in the Virtualization Manager

Perform backups in the Virtualization Manager

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,145 Votes: 1 Revisions: 10

Most customers backup Virtualization Manager on the hypervisor level, using the same methodology as for other virtual machines.

Note: This provides general backup information and does not provide specific commands.

If you do not want to back up the Virtualization Manager appliance from the hypervisor level, use the information below to perform backups from within the appliance.  You can use two different methods to backup your data:

  • Install a backup agent
  • Perform manual backups

Note: You do not need to backup federated collector appliances as no data is stored there.  You may want to backup any custom configurations.

Install a Backup Agent

Note: SolarWinds does not provide recommendations or support for backup agents.


  1. Install a backup agent on the appliance.
    The Virtualization Manager appliance uses a minimal install version of CentOS 5.4, 64-bit, which is 100% binary compatible with Red Hat Advanced Server 5.4. You can install backup agents for either install.

    You may need to install additional OS modules to support your chosen backup agent which are available from the CentOS website.
  2. Follow the instructions for the backup agent you install.


Perform Manual Backups

You can also back up the Virtualization Manager data necessary to recreate the data set. Backup the following information:

  • configuration files in /etc/hyper9/
  • The PostgreSQL database

Note:  The Lucene search indexes used by the product can be recreated from the PostgreSQL database and do not need to be included in your backup procedures.

  1. Copy the configuration files from the /etc/hyper9 directory to a backup location.
  2. Export the data in the postgreSQL database to a backup location. The product uses the PostgreSQL user h9pgsu and the schema name hyper9db.
    You can find scripts to automate exports from the PostgreSQL database online. See the PostgreSQL documentation for more information. 
Last modified