4.12 Backing Up Oracle VM Manager

To back up Oracle VM Manager, you should back up the Oracle VM Manager configuration file, and the Oracle VM Manager database schema. By default, this schema is named OVS, and this is used in the backup example. Replace the schema name with your own.

The Oracle VM Manager configuration file is stored in this location:


This configuration file contains database connection information, ports and the UUID used by Oracle VM Manager. An example of this configuration file follows:

Example 4.4 Oracle VM Manager configuration file

DBHOST=<hostname of database server>
SID=<oracle SID>
LSNR=<listener port number defaults 1521>
APEX=<application express port number defaults 8080>
OVSSCHEMA=<database schema name for oracle vm manager defaults ovs>
WLSADMIN=<weblogic server admin defaults weblogic>
OVSADMIN=<oracle vm manager administrator name defaults admin>
COREPORT=<oracle vm manager core port defaults 54321>
UUID=<oracle vm manager uuid>

To back up Oracle VM Manager:

  1. Back up/copy the Oracle VM Manager configuration file located at


  2. Back up the Oracle VM Manager database OVS schema. Run the Oracle Database EXP utility to export the OVS schema if you are using an Oracle Database. For installations of Oracle VM Manager that use a MySQL database, the entire database is backed up automatically every 24 hours using the MySQL Enterprise Backup utility, but it is also possible to perform a manual backup. See Appendix B, Oracle VM Manager MySQL Backup and Restore for more information on Oracle VM Manager MySQL database backup and restore facilities.


If you are using an Oracle Database for Oracle VM Manager it is imperative that you ensure that there is a regular backup strategy in place for the database. While Oracle VM Manager is able to automate backups for a locally hosted MySQL database, it is unable to handle backups for an externally hosted Oracle Database. Without an adequate backup of the database, it is very unlikely that you will be able to restore your environment cleanly in the event of database corruption or failure.