A Bridge to the Cloud...

ovm-bkp v1.1.0: Virtual Machine Backup for Oracle VM 3.4

Simon Coter
Senior Manager, Oracle Linux and Virtualization Product Management

Target of those utilities is to manage Virtual Machine Backups on Oracle VM 3.4; based on scripts installed on Oracle VM Manager Instance, ovm-bkp allows to easily manage backups and restore of Virtual Machines running on Oracle VM 3.4.

This project, started years ago, evolved in the time thanks to the feedback received on my personal blog. ovm-bkp v1.1 introduced one important new feature, compared to the old 1.0.1 release:

  • vDisk exclude option: so, the option to exclude one or more Virtual Disk(s) from the Virtual Machine backup executed

This little enhancement, at the end, allows for example to skip the virtual-disk(s) where the Oracle Database is running, also because the best and suggested way to backup the Oracle Database remains RMAN (Recovery Manager). 

Here, just a quick reminder of the solution architecture:

"ovm-bkp v1.1.0" is now available on Oracle Technology Network website under the "Oracle VM Tools" group; at the same page you can also find the "Installation and User Guide for ovm-bkp v1.1.0 Backup Utilities".

"ovm-bkp v1.1.0" is based on an RPM for Oracle Linux 6 and 7 and needs to be installed on Oracle VM Manager instance/machine:

Feel free to leave your feedback on this blog entry for possible issues and/or request for enhancement.

Join the discussion

Comments ( 23 )
  • Michal Friday, February 22, 2019
    Dear Simon
    Hood job.

  • Michele Vecchiato Saturday, February 23, 2019
    Excellent work and very comfortable!

    #1 It's tested on Oracle Exadata Virtualized (by OVM for x64) Environment ?

    #2 When the same thing will be for Oracle VM server for SPARC ?

    Best Regards

    Michele V.
  • Simon Monday, February 25, 2019
    Hi Michele,

    #1 This script relies on Oracle VM Manager CLI, component that it's not part of Exadata with Oracle VM onboard.

    #2 Actually no ETA for that.

  • Daniele Bocciolini Monday, February 25, 2019
  • Rene Vallant Tuesday, March 5, 2019
    I have a strange behavior, where you may have a solution.
    For some vm I get the error message:
    ERROR: Virtual Machine VDCSLINORA92 owns only physical disks - hot-clone not possible

    But there are only virtual disks assigned to this vm ....

    Thx + BR
  • Simon Tuesday, March 5, 2019
    Hi Rene,

    I'm going to release an updated release of the script (v. 1.1.0c) where I've addressed a couple of issues.
    One of those should be what you've encountered.
    The updated release should be available with 24 hours.

  • Simon Wednesday, March 6, 2019

    release 1.1.0c-20190305 is now public available.

  • Bala Ullikanti Tuesday, March 19, 2019
    Thanks this is helpful especially snap capabilities.

    would be great if these features get integrated with OVMM GUI.
  • Simon Tuesday, March 19, 2019
    Hi Bala,

    thanks for your feedback.
    I'll take into consideration your request.

  • Carlos Wednesday, March 20, 2019
    Hi Simon, i got a different kind of issue. We had to restore the ovm manager database and now we lost all the backup configuration. All the files remain on the NFS Repo but we are not able to list them with ./ovm_listbackup script. There is any way to get them back.
  • Simon Wednesday, March 20, 2019
    Hi Carlos,

    ./ovm_listbackup script looks for VMs that:

    - contain the name of the VM
    - have a proper "TAG" associated to the VM

    So, if for example, your VM Backup name is:


    you will have to add a tag named:


    to get it recognized as a backup.
    Hope this helps.

  • Sasi Saturday, April 6, 2019
    I need guidance on configuring this backup tool.
    When i execute ./ovm-setup-vm.sh with VM name, retention & target_repository.

    Am getting following error message.

    The is local disk.

    Invalid repository name: /local_data/vm_backup_test/
  • Simon Tuesday, April 9, 2019
    Hi Sasi,

    please, see the installation/user guide (also if you execute the ./ovm-backup.sh script you'll see some examples).
    The target-repository has to be an OVM repository (in your case NFS) and, to the script, you have to pass the repository name.

  • Guest user Tuesday, May 14, 2019
    Hello Simon

    We have installed the latest version of the backup tool.
    When I start a backup it does not complete
    and keeps running with the following message
    Waiting for Vm moving to complete...... seconds
    until interrupted.
    In the manager console there is this error

    OVMRU_007013E Cannot thin clone: disk, to: REPO. The clone target does not support thin cloning.

    The Vm ( OL7) is not running. Both disk and backup repo are on nfs storage.

    Do you have any idea what is wrong?

    Kind regards
  • Simon Thursday, May 16, 2019
    Hi Bert,

    the backup-tool requires to have the source-VM on a repository created on FC/iSCSI storage.
    That said, thanks for your message here because, based on this, I can try to improve error messaging within the script.

  • Guest user Friday, May 17, 2019
    Hi Simon,

    Thank you for your reply
    However, from the assumption section in the installation and user guide I would think that Vm's on NFS repository's can be backupped if stopped. Is this not so?

    Best regards

    Virtual Machines running on NFS repositories have to be stopped.
  • Simon Wednesday, May 22, 2019

    I've just sent an email to you to debug the NFS issue.

  • Simon Wednesday, May 22, 2019
    while having VMs on NFS repo we cannot use thin-clones.
    So the work-around to this limitation is to change following line into the “ovm-backup.sh” script:



  • Phil S Thursday, August 8, 2019
    This looks like a great product. IS it intended as a daily backup utility perhaps executed via cron?

    Our PCA environment utilizes NFS shares on ZFS Storage arrays for the OVM repositories on which our VMs reside. That being the case we would have to shut down production VMs to back them up via ovm-bkp...which is not practical.

    Why is backup of running VMs on NFS repositories not supported?

    Are there plans to add support to backup running VMs on NFS repositories in the near future?

    Thank you
  • Simon Thursday, August 8, 2019
    Hi Phil,

    the script can be scheduled by your preferences by cron.
    That said, the backup cannot be managed on running VMs that reside on NFS repositories just because the hot-clone relies on ocfs2 ref-link feature (that, obviously, requires iSCSI / FC storage).
    I do not think that this script can be extended to NFS for backups for running VMs.

  • Phil S Friday, August 9, 2019
    Simon - Thank you for your quick response and explanation. Our search for an OVM on NFS backup solution continues...

    I'm open to any suggestions and recommendations you might have.

    Thank you,
  • Igor Thursday, March 19, 2020
    Hi Simon,
    I'm having problems with the "disk-slot-to-exclude" option. I would like to skip the backup of the disk where the data is located because the backup of that disk is already resolved. The configuration is correct, however the backup still copies that disk. Is it possible that the problem is if I have empty slots between disks - specifically, slots 0,1 and 8 (in VM manager) are filled and I want to skip disk 8. In the log file is that disk number 3?

    Thank you

    VmDiskMapping 1 = 0004fb0000130000d6dc8c5d59f4b861 [Disk Mapping for Id (0004fb0000120000fb8dc3c698078bed.img)] 15 GB
       VmDiskMapping 2 = 0004fb0000130000f5927e2a9ffd604e [Disk Mapping for Id (0004fb00001200000d87f5ec4ba308a5.img)] 50 GB
       VmDiskMapping 3 = 0004fb000013000053ff3d2df6b0b9e3 [Mapping for disk Id (0004fb00001200008670f1373b5ddcd9.img)] 700 GB
  • Igor Friday, April 10, 2020
    Hi Simon,

    here I'm again :)
    It really doesn't work when slots are skipped. I repeated the server backup which has disks in slots 0,1,2 and 8. when I specify a disk to exclude 2.8 skips only disk 2, and disk 8 is copied to backup. However, if I specify disk to exclude 2,3 it skips disk 2 and disk 8.
    It's a kind of workround, but if you can do it, you might want to fix it.

    Thanks and best regards, Igor
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.