{"id":21133,"date":"2022-12-21T10:52:01","date_gmt":"2022-12-21T09:52:01","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=21133"},"modified":"2022-12-21T10:52:05","modified_gmt":"2022-12-21T09:52:05","slug":"high-availability-vms-on-oda","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/","title":{"rendered":"High Availability VMs on ODA"},"content":{"rendered":"\n<p>Virtualisation is now possible on the ODA whatever it is an ODA Lite or HA. The virtualisation is based on KVM and integrated with odacli for Bare Metal installation. Virtualisation has got the advantage to allocate resources to databases and applications on the same physical server. But what is the High Availability solution I have for virtualization on the ODA?<\/p>\n\n\n\n<!--more-->\n\n\n\n<h2 class=\"wp-block-heading\">Virtualisation solutions<\/h2>\n\n\n\n<p>There is 2 kind of virtualisation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Virtual Machines<\/h3>\n\n\n\n<p>Virtual Machines is also called Compute Instances.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>These VM are mainly used for application<\/li>\n\n\n\n<li>They support various OS like linux, windows, solaris, &#8230;<\/li>\n<\/ul>\n\n\n\n<p>In order to be able to create a Compute Instance, we need :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A CPU Pool<\/li>\n\n\n\n<li>A VM Storage<\/li>\n\n\n\n<li>Virtual Network<\/li>\n\n\n\n<li>Virtual Disks<\/li>\n<\/ul>\n\n\n\n<p><strong>VM Storage:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Central location storing resources essential for creating and managing VM as ISO files, VM configuration files, Virtual Disks<\/li>\n\n\n\n<li>Created on the ACFS it can be easily relocate in case the physical server, where the VM is running, fails<\/li>\n<\/ul>\n\n\n\n<p><strong>Virtual Network:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Bridged or a bridged-vlan<\/li>\n\n\n\n<li>Attached on one of the bonding interface<\/li>\n\n\n\n<li>Additional bridged network can be created on interfaces except the public interface<\/li>\n\n\n\n<li>Additional bridged-vlan network can be created on any interface including the public interface<\/li>\n\n\n\n<li>Bridge with or with IP assigned<\/li>\n\n\n\n<li>For more information, see my other blog on this subject <a href=\"https:\/\/blog.dbi-services.com\/creating-kvm-database-system-on-separate-vlan-network-on-oda\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/blog.dbi-services.com\/creating-kvm-database-system-on-separate-vlan-network-on-oda\/<\/a><\/li>\n<\/ul>\n\n\n\n<p><strong>A Virtual Disks is:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Created in VM storage<\/li>\n\n\n\n<li>Provides additional storage to the VM<\/li>\n\n\n\n<li>Can be attached and detach later on<\/li>\n\n\n\n<li>Expanding VM file system storage or creating a new file system<\/li>\n<\/ul>\n\n\n\n<br>\n\n\n\n<p>A Compute Instance can be started, stopped, cloned and restarted independently.<\/p>\n\n\n\n<p>Auto start can be enabled or disabled whatever ODA we are using (Single-node or HA ODA models), see below :<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4,8,21,41]\">[root@dbioda02 ~]# odacli describe-vm -n vmdoag | grep -i 'Auto Start'\n               Auto start:  YES\n               \n[root@dbioda02 ~]# odacli modify-vm -h | grep -i 'autostart'\n    --autostart,-as            Enables autostart for the VM\n    --no-autostart,-no-as      Disables autostart for the VM\n    \n[root@dbioda02 ~]# odacli modify-vm -n vmdoag -no-as\n\nJob details\n----------------------------------------------------------------\n                     ID:  8cce5d5a-3f84-4140-a3eb-13646db774bc\n            Description:  VM vmdoag modification\n                 Status:  Created\n                Created:  December 20, 2022 4:07:37 PM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\n\n[root@dbioda02 ~]# odacli describe-job -i 8cce5d5a-3f84-4140-a3eb-13646db774bc\n\nJob details\n----------------------------------------------------------------\n                     ID:  8cce5d5a-3f84-4140-a3eb-13646db774bc\n            Description:  VM vmdoag modification\n                 Status:  Success\n                Created:  December 20, 2022 4:07:37 PM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nValidate dependency resources            December 20, 2022 4:07:37 PM CET    December 20, 2022 4:07:38 PM CET    Success\nDefine VM locally                        December 20, 2022 4:07:38 PM CET    December 20, 2022 4:07:38 PM CET    Success\nEdit VM CRS Configuration                December 20, 2022 4:07:38 PM CET    December 20, 2022 4:07:38 PM CET    Success\nSave domain in ACFS                      December 20, 2022 4:07:38 PM CET    December 20, 2022 4:07:38 PM CET    Success\nDefine VM globally                       December 20, 2022 4:07:38 PM CET    December 20, 2022 4:07:38 PM CET    Success\nModify VM metadata                       December 20, 2022 4:07:38 PM CET    December 20, 2022 4:07:38 PM CET    Success\nPersist metadata                         December 20, 2022 4:07:38 PM CET    December 20, 2022 4:07:39 PM CET    Success\n\n[root@dbioda02 ~]# odacli describe-vm -n vmdoag | grep -i 'Auto Start'\n               Auto start:  NO\n<\/pre>\n<br>\n\n\n\n<h3 class=\"wp-block-heading\">DB Systems<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>These VM are dedicated to host database<\/li>\n\n\n\n<li>Hard partitioning is possible<\/li>\n\n\n\n<li>It is like an odacli integrated in the Bare Metal itself<\/li>\n\n\n\n<li>It will permit network segregation and OS segregation<\/li>\n\n\n\n<li>They are mainly used for licensing reason in Enterprise Edition. CPU core of the ODA will not be reduced. Shared DB System CPU pool will be created according to the number of cores being licensed, and DB System will be run on those CPU Pool.<\/li>\n<\/ul>\n\n\n\n<p>For DB Systems there is a few requirement that needs to be understood:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>200 GB per DB System will be needed on the DATA Group to create the virtual host<\/li>\n\n\n\n<li>We can only host 1 database per DB System<\/li>\n\n\n\n<li>Database created in the DB System can only run ASM and not ACFS<\/li>\n\n\n\n<li>In version 19.X it possible to create CDB or non CDB database<\/li>\n\n\n\n<li>With current ODA 19.17 version it is possible to create database in DB System in versions 21.8, 21.7, 21.6, 21.5, 21.4, 19.17, 19.16, 19.15, 19.14, and 19.13.<\/li>\n<\/ul>\n\n\n\n<p>On the other hand the DB System will required a more complex installation, will use more resources (Memory and CPU) and add more maintenance work (during ODA patching we will need to additionally patch all DB Systems).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">High Availability with Compute Instance<\/h2>\n\n\n\n<p>HA (High Availability) is only possible with ODA HA models (2 nodes with ACFS Storage).<br>By default VM are created with autostart and failover enabled for HA models:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">[root@dbioda02 ~]# odacli describe-vm -n vmdoag | grep -i 'Auto Start\\|Fail over'\n               Auto start:  YES\n                Fail over:  YES\n<\/pre>\n<br>\n\n\n\n<p>It is of course possible to enable or disable failover option.<\/p>\n\n\n\n<p><strong>What is happening in case the physical node, where the VM is running, is crashing ?<\/strong><br>There will be one attempt to restart the VM once before failing over to the different node on HA models.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Relocate VM<\/h3>\n\n\n\n<p>We can easily relocate the VM on the other node. Currently my VM is running on node 0, named, dbioda02.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@dbioda02 ~]# odacli describe-vm -n vmdoag | grep -i node\n             Current node:  dbioda02\n           Preferred node:  dbioda02\n<\/pre>\n<\/br>\n\n\n\n<p>As we can see, we can set a preferred node. This preferred node can be easily change.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@dbioda02 ~]# odacli modify-vm -h | grep -i pref-node\n    --pref-node,-pn            Defines the preferred node to run the VM, use\n<\/pre>\n<\/br>\n\n\n\n<p>To be able to relocate the VM on the other node the graphical settings should be put on 127.0.0.1 if not already done, otherwise the command will failed with following error : <\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>internal error: qemu unexpectedly closed the monitor: 2022-09-12T21:05:45.531641Z qemu-system-x86_64: -vnc 10.36.0.232:0: Failed to bind socket: Cannot assign requested address<\/code><\/pre>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@dbioda02 ~]# odacli modify-vm -n vmdoag -g \"vnc,listen=127.0.0.1\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  74028fc9-d680-4565-ba94-cce0d0bb5677\n            Description:  VM vmdoag modification\n                 Status:  Created\n                Created:  December 21, 2022 8:35:50 AM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\n<\/pre>\n<\/br>\n\n\n\n<p>To relocate the VM on the other node, either we can stop the VM and start it on the other node :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli start-vm -n vmdoag -nn dbioda03<\/code><\/pre>\n\n\n\n<p>Or use the migrate command :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli migrate-vm -n vmdoag -to dbioda03<\/code><\/pre>\n\n\n\n<p>Currently my VMs is running on my node 0, dbioda02, my node 1 being dbioda03. Pay attention on which nodes, the KVM processes are running.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,9]\">\n[root@dbioda02 ~]# ps -ef | grep -i [k]vm\nqemu     36043     1  0 Dec20 ?        00:08:42 \/usr\/bin\/qemu-system-x86_64 -name guest=vmdoag,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=\/var\/lib\/libvirt\/qemu\/domain-2-vmdoag\/master-key.aes -enable-fips -machine pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -cpu Haswell-noTSX-IBRS -m 6144 -overcommit mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid d71ecbc9-30f6-43c6-b6ea-7649fffa60b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=36,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x4.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x4 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x4.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x4.0x2 -blockdev {\"driver\":\"file\",\"filename\":\"\/u05\/app\/sharedrepo\/vmsdoag\/.ACFS\/snaps\/vm_vmdoag\/vmdoag\",\"node-name\":\"libvirt-2-storage\",\"auto-read-only\":true,\"discard\":\"unmap\"} -blockdev {\"node-name\":\"libvirt-2-format\",\"read-only\":false,\"driver\":\"qcow2\",\"file\":\"libvirt-2-storage\",\"backing\":null} -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=libvirt-2-format,id=virtio-disk0,bootindex=1 -device ide-cd,bus=ide.0,unit=0,id=ide0-0-0 -netdev tap,fd=38,id=hostnet0,vhost=on,vhostfd=39 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:3c:2a:60,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 10.36.0.232:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on\nroot     36047     2  0 Dec20 ?        00:00:00 [kvm-nx-lpage-re]\nroot     36053     2  0 Dec20 ?        00:00:00 [kvm-pit\/36043]\n\n[root@dbioda03 ~]# ps -ef | grep -i [k]vm\n[root@dbioda03 ~]#\n<\/pre>\n<\/br>\n\n\n\n<p>Let&#8217;s relocate the VM on dbioda03 node.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,14]\">\n[root@dbioda02 ~]# odacli migrate-vm -n vmdoag -to dbioda03\n\nJob details\n----------------------------------------------------------------\n                     ID:  ab5c7fd2-f21b-4f0d-af70-34747e333e75\n            Description:  VM vmdoag migration\n                 Status:  Created\n                Created:  December 21, 2022 8:49:08 AM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\n\n[root@dbioda02 ~]# odacli describe-job -i ab5c7fd2-f21b-4f0d-af70-34747e333e75\n\nJob details\n----------------------------------------------------------------\n                     ID:  ab5c7fd2-f21b-4f0d-af70-34747e333e75\n            Description:  VM vmdoag migration\n                 Status:  Success\n                Created:  December 21, 2022 8:49:08 AM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nValidate migrate prerequisites           December 21, 2022 8:49:08 AM CET    December 21, 2022 8:49:08 AM CET    Success\nMigrate VM                               December 21, 2022 8:49:08 AM CET    December 21, 2022 8:49:26 AM CET    Success\n<\/pre>\n<\/br>\n\n\n\n<p>Let&#8217;s check the details for the VM to confirm the current node information.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@dbioda02 ~]# odacli describe-vm -n vmdoag | grep -i node\n             Display Port:  Check node dbioda03\n             Current node:  dbioda03\n           Preferred node:  dbioda02\n<\/pre>\n<\/br>\n\n\n\n<p>The current node is now dbioda03.<\/p>\n\n\n\n<p>Let&#8217;s check that the KVM processes are really running on dbiod03 node.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4]\">\n[root@dbioda02 ~]# ps -ef | grep -i [k]vm\n[root@dbioda02 ~]#\n\n[root@dbioda03 ~]# ps -ef | grep -i [k]vm\nqemu     76320     1  4 08:49 ?        00:00:54 \/usr\/bin\/qemu-system-x86_64 -name guest=vmdoag,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=\/var\/lib\/libvirt\/qemu\/domain-1-vmdoag\/master-key.aes -enable-fips -machine pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -cpu Haswell-noTSX-IBRS -m 6144 -overcommit mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid d71ecbc9-30f6-43c6-b6ea-7649fffa60b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=36,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x4.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x4 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x4.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x4.0x2 -blockdev {\"driver\":\"file\",\"filename\":\"\/u05\/app\/sharedrepo\/vmsdoag\/.ACFS\/snaps\/vm_vmdoag\/vmdoag\",\"node-name\":\"libvirt-2-storage\",\"auto-read-only\":true,\"discard\":\"unmap\"} -blockdev {\"node-name\":\"libvirt-2-format\",\"read-only\":false,\"driver\":\"qcow2\",\"file\":\"libvirt-2-storage\",\"backing\":null} -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=libvirt-2-format,id=virtio-disk0,bootindex=1 -device ide-cd,bus=ide.0,unit=0,id=ide0-0-0 -netdev tap,fd=38,id=hostnet0,vhost=on,vhostfd=39 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:3c:2a:60,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on\nroot     76336     2  0 08:49 ?        00:00:00 [kvm-nx-lpage-re]\nroot     76342     2  0 08:49 ?        00:00:00 [kvm-pit\/76320]\n<\/pre>\n<\/br>\n\n\n\n<p>Let&#8217;s crash dbiod03 node and see if a failover of the VM is automatically done on the dbioda02 node.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@dbioda03 ~]# systemctl poweroff\nConnection to 10.36.0.233 closed by remote host.\nConnection to 10.36.0.233 closed.\n<\/pre>\n<\/br>\n\n\n\n<p>We can see that the KVM processes have been automatically started on dbioda02 node.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@dbioda02 ~]# ps -ef | grep -i [k]vm\nqemu     19412     1 18 09:12 ?        00:00:46 \/usr\/bin\/qemu-system-x86_64 -name guest=vmdoag,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=\/var\/lib\/libvirt\/qemu\/domain-3-vmdoag\/master-key.aes -enable-fips -machine pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -cpu Haswell-noTSX-IBRS -m 6144 -overcommit mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid d71ecbc9-30f6-43c6-b6ea-7649fffa60b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=36,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x4.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x4 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x4.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x4.0x2 -blockdev {\"driver\":\"file\",\"filename\":\"\/u05\/app\/sharedrepo\/vmsdoag\/.ACFS\/snaps\/vm_vmdoag\/vmdoag\",\"node-name\":\"libvirt-2-storage\",\"auto-read-only\":true,\"discard\":\"unmap\"} -blockdev {\"node-name\":\"libvirt-2-format\",\"read-only\":false,\"driver\":\"qcow2\",\"file\":\"libvirt-2-storage\",\"backing\":null} -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=libvirt-2-format,id=virtio-disk0,bootindex=1 -device ide-cd,bus=ide.0,unit=0,id=ide0-0-0 -netdev tap,fd=38,id=hostnet0,vhost=on,vhostfd=39 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:3c:2a:60,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on\nroot     19427     2  0 09:12 ?        00:00:00 [kvm-nx-lpage-re]\nroot     19433     2  0 09:12 ?        00:00:00 [kvm-pit\/19412]\n<\/pre>\n<\/br>\n\n\n\n<p>Following automatic failover, and due to the fact dbioda03 node is still power off, the VM description is showing current node as N\/A.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@dbioda02 ~]# odacli describe-vm -n vmdoag | grep -i node\n             Current node:  N\/A\n           Preferred node:  dbioda02\n<\/pre>\n<\/br>\n\n\n\n<p>Once dbioda03 node is up and running again, the output is showing correctly dbioda02 node as current node.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\n[root@dbioda02 ~]# odacli describe-vm -n vmdoag | grep -i node\n             Current node:  dbioda02\n           Preferred node:  dbioda02\n<\/pre>\n<\/br>\n\n\n\n<h2 class=\"wp-block-heading\">High Availability with DB Systems<\/h2>\n\n\n\n<p>With DB Systems we can either create a single-instance database or a RAC database with 2 instances. We will the benefit here from the RAC advantages for DB Systems High Availability.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Virtualisation is now possible on the ODA whatever it is an ODA Lite or HA. The virtualisation is based on KVM and integrated with odacli for Bare Metal installation. Virtualisation has got the advantage to allocate resources to databases and applications on the same physical server. But what is the High Availability solution I have [&hellip;]<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[871,2567,96,2655],"type_dbi":[],"class_list":["post-21133","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-ha","tag-oda-2","tag-oracle","tag-vm"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>High Availability VMs on ODA - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"High Availability VMs on ODA\" \/>\n<meta property=\"og:description\" content=\"Virtualisation is now possible on the ODA whatever it is an ODA Lite or HA. The virtualisation is based on KVM and integrated with odacli for Bare Metal installation. Virtualisation has got the advantage to allocate resources to databases and applications on the same physical server. But what is the High Availability solution I have [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-12-21T09:52:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-12-21T09:52:05+00:00\" \/>\n<meta name=\"author\" content=\"Marc Wagner\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Marc Wagner\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"High Availability VMs on ODA\",\"datePublished\":\"2022-12-21T09:52:01+00:00\",\"dateModified\":\"2022-12-21T09:52:05+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/\"},\"wordCount\":818,\"commentCount\":4,\"keywords\":[\"HA\",\"oda\",\"Oracle\",\"VM\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/\",\"name\":\"High Availability VMs on ODA - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2022-12-21T09:52:01+00:00\",\"dateModified\":\"2022-12-21T09:52:05+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"High Availability VMs on ODA\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\",\"name\":\"Marc Wagner\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"caption\":\"Marc Wagner\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"High Availability VMs on ODA - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/","og_locale":"en_US","og_type":"article","og_title":"High Availability VMs on ODA","og_description":"Virtualisation is now possible on the ODA whatever it is an ODA Lite or HA. The virtualisation is based on KVM and integrated with odacli for Bare Metal installation. Virtualisation has got the advantage to allocate resources to databases and applications on the same physical server. But what is the High Availability solution I have [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/","og_site_name":"dbi Blog","article_published_time":"2022-12-21T09:52:01+00:00","article_modified_time":"2022-12-21T09:52:05+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"High Availability VMs on ODA","datePublished":"2022-12-21T09:52:01+00:00","dateModified":"2022-12-21T09:52:05+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/"},"wordCount":818,"commentCount":4,"keywords":["HA","oda","Oracle","VM"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/","url":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/","name":"High Availability VMs on ODA - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-12-21T09:52:01+00:00","dateModified":"2022-12-21T09:52:05+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/high-availability-vms-on-oda\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"High Availability VMs on ODA"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628","name":"Marc Wagner","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","caption":"Marc Wagner"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/21133","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=21133"}],"version-history":[{"count":33,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/21133\/revisions"}],"predecessor-version":[{"id":21173,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/21133\/revisions\/21173"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=21133"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=21133"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=21133"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=21133"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}