To restore Oracle VM Manager from a backup:

1. First, if you need to reinstall or upgrade Oracle VM Manager, use the Oracle VM Manager installation media to perform an install or upgrade of the software on your server. See Installing Oracle VM Manager for information on how to perform the installation. See Upgrading Oracle VM Manager for information on how to perform the upgrade.

   You should perform the install using the runInstaller.sh --uuid uuid command and provide the UUID from the previous manager installation you created a backup from. The UUID can be found in the Oracle VM Manager configuration file.

   Note

   The Oracle VM Manager UUID is also persisted in the /etc/sysconfig/ovmm file on Linux, and in the /etc/opt/ovmm file on Solaris. If the system disk of the server on which you are installing or restoring Oracle VM Manager was not wiped entirely, the existing UUID is still present and will be detected when running the installer.

   • The --uuid option on Linux overrides this existing UUID. Solaris users must use the shortened form of this option: -u.

   • If no UUID is present in /etc/sysconfig/ovmm, the --uuid option adds the UUID to the file on Linux. On Solaris, the -u option adds the UUID to /etc/opt/ovmm if the UUID is not present in this file.

   An example install command syntax for Linux is as shown in this example:

   # ./runInstaller.sh --uuid 0004FB000000100002CB7F2DFFA8D8

   When the Oracle VM Manager installer prompts for installation information other than passwords, reuse the same usernames for the database schema, Oracle WebLogic Server and Oracle VM Manager administration user, as set out in the backup of the Oracle VM Manager configuration file. You must set the passwords again as the passwords are not backed up and cannot be restored.

2. After installation, reinstallation or upgrade, stop the Oracle VM Manager Command Line Interface, Oracle VM Manager, and the database before you restore the backup. On Linux:

   # /sbin/service ovmcli stop
   # /sbin/service ovmm stop
   # /sbin/service ovmm_mysql stop 

3. Before you restore the database, ensure that no database files already exist on the Oracle VM Manager host:

   # cd /u01/app/oracle/mysql/data/
   # rm -rf appfw ibdata1 ib_logfile0 ib_logfile1 mysql ovs performance_schema

   Important

   Do not remove any of the following files from /u01/app/oracle/mysql/data/:

   • auto.cnf

   • my.cnf

   • .mysqlconfig

   • mysql_upgrade_info

     This file may only exist if there was an upgrade to the current version. It does not exist on systems where a fresh installation was performed.

4. To initiate the database restore, as the oracle user, use the RestoreDatabase command located in /u01/app/oracle/ovm-manager-3/ovm_tools/bin, for example:

   # su - oracle
   $ bash /u01/app/oracle/ovm-manager-3/ovm_tools/bin/RestoreDatabase.sh \
        ManualBackup-20140324_102412
   INFO: Expanding the backup image...
   INFO: Applying logs to the backup snapshot...
   INFO: Restoring the backup...
   INFO: Restoring OVM keystores and certificates
   INFO: Success - Done!
   INFO: Log of operations performed is available at: 
   /u01/app/oracle/mysql/dbbackup/ManualBackup-20140324_102412/Restore.log
   
   
   IMPORTANT:
   
         As 'root', please start the OVM Manager database and application using:
                  service ovmm_mysql start; service ovmm start
           

   The RestoreDatabase script expects the name of the directory for a particular backup directory as described in Section 5.1.2.1, “Backing up Directories and Logs”. You do not need to specify the full path to the backup directory as this is already specified in the DBBACKUP variable.

5. Restart the database and Oracle VM Manager, and the Oracle VM Manager Command Line Interface. On Linux:

   # /sbin/service ovmm_mysql start
   # /sbin/service ovmm start 
   # /sbin/service ovmcli start 

6. Since the certificates required to authenticate various components, such as the Oracle VM Manager Web Interface and Oracle VM Manager Command Line Interface, are regenerated during the new installation and the mappings for these are overwritten by the database restore, it is necessary to reconfigure the certificates used to authenticate these components. This is achieved by running the following script to reconfigure the Oracle WebLogic Server:

   # export MW_HOME=/u01/app/oracle/Middleware
   # /u01/app/oracle/ovm-manager-3/ovm_upgrade/bin/ovmkeytool.sh setupWebLogic

   For more information on the ovmkeytool.sh script, please see Section 1.2.3, “Setting up SSL on Oracle VM Manager”.

   Once you have run this command, you must restart Oracle VM Manager and then run the client certificate configuration script. On Linux:

   # /sbin/service ovmm restart
   # /u01/app/oracle/ovm-manager-3/bin/configure_client_cert_login.sh

   The script requires that Oracle VM Manager is running, and prompts you for the administrator username and password that should be used to access Oracle VM Manager. The script makes changes that may require Oracle VM Manager to be restarted:

   # /sbin/service ovmm restart

7. Within Oracle VM Manager go to the Servers and VMs tab and perform a Refresh All on your existing server pools. See Refresh All in the Oracle VM Manager User's Guide for more information on these options.