Category: Best Practices

If you haven’t checked out the latest Oracle 11gR2 ( VM template, it can be found at

Once there, under ‘Select a Product Pack’, pick Oracle VM Templates, and under ‘Platform’ pick your achitecture, 32 bit or 64 bit. Then look for the template labeled: Oracle VM Templates for Oracle RAC 11gR2 Media Pack v1 for x86 (32 bit) or Oracle VM Templates for Oracle RAC 11gR2 Media Pack v1 for x86_64

The 11gR2 templates are linked on OTN at:

However, if your looking for the 11gR2 ( Oracle VM template, it requires you have access to My Oracle Support. Only customers with support can download the under the patch number 10113572

If you want to know more about how the templates work and have access to Oracle OpenWorld on Demand, once logged in go to the search navigation bar and type ‘Oracle VM Best Practices’, once there you will find our (Saar Maoz and Roger Lopez) session presentation slide deck as well as audio to accompany the slide deck. Saar did a great job on creating these templates and it truly shows. I hope you all can check them out!

If you do not have access to download the presentation but want a copy, feel free to comment on this post so I can get you a copy.


In today’s topic, I’d like to discuss the process of backing up and restoring your Oracle VM Manager. Since the Oracle VM Manager is used to manage all your virtual machines and virtual machine resources, I thought it would be a good exercise to discuss the step-by-step process on backing up and restoring the OVM Manager environment. It is crucial to make backups of your Oracle VM Manager to ensure that you don’t lose any data from the Oracle VM Manager repository database that could cause you a headache in having to actively restore each virtual machine to a new Oracle VM Manager, one by one (not a fun exercise). The good news is Oracle has made the backup-restore process quite easy. In the example below, I will be backing up my original Oracle VM Manager, and restoring the content from my old server it into a new server all that has a fresh install of Oracle VM Manager.

Continue reading

In one of my earlier posts, I discussed setting up a shared storage repository using OCFS2. Today, I’d like to discuss the steps involved in implementing additional repositories to your Oracle VM Server. One of the main reasons you would want to add an additional repository is the simple fact of not having additional space within your current OVS repository to host more virtual machines. In this tutorial, I’ll show you step by step on how to do just that.


When working with Oracle databases, it is highly recommended to use physical volumes attached to your virtual machines instead of shared virtual disks due to degraded performance when using virtual disks. Unfortunately, within the Oracle VM Manager you cannot add physical volumes to your virtual machine unlike shared virtual disks. In order to add physical disks to a virtual machine you must modify a VM’s vm.cfg file located under /OVS/running_pool/<vm_name>/. This directory contains a System.img file, a vm.cfg file, and a vm.cfg.orig file. An example of a basic vm.cfg file created by the OVM Manager looks like the following:


Oracle VM uses Oracle VM Server (OVS) repositories to store resources such as virtual machines, templates, ISO images, and shared virtual disks. Once a storage repository has been created and initialized, it will create storage repository directories to store these resources. One of these sub-directories is the running_pool directory which will contain your virtual machines. Via your Server Pool Master you will create an OVS repository following the steps below.


 Oracle VM’s architecture provides the same native bonding module that is found in all Enterprise Linux 5.x distributions. Although bonding has several different modes which include modes such as the round robin policy and load balancing policy, the active-backup policy (mode 1) is the preferred mode for Oracle RAC interconnects. The active-backup policy has only one active slave and the remaining are passive slaves. One of the other slaves will become active, if and only if, there is a failure with the current active slave within the bond.

In order to setup bonding within the OVM environment, the first step is to stop any guest VMs that are currently running. Once you have stopped all guest VMs, you must stop all network bridges within your OVM environment using the following command

/etc/xen/scripts/./network-bridges stop
The network-bridges script controls the creation of your network bridges for each physical NIC. The default behavior of OVM is to create a xen bridge for each physical NIC.
In the following example, we will start configuring our bond0 device and enslave two NIC adapters (eth1 and eth2) to our bond device.