17 Migrating from Virtualized Platform to KVM on Oracle Database Appliance
Understand how you can migrate your Oracle Database Appliance deployment from virtualized platform to KVM.
- About Migrating Oracle Database Appliance from Virtualized Platform to KVM
Understand how you can migrate your virtualized platform deployment to KVM. - Migrating from Virtualized Platform to KVM on Oracle Database Appliance
Understand the procedure to migrate from Virtualized Platform to KVM on Oracle Database Appliance.
About Migrating Oracle Database Appliance from Virtualized Platform to KVM
Understand how you can migrate your virtualized platform deployment to KVM.
You can migrate your Oracle Database Appliance virtualized platform deployment to KVM using the Data Preserving Reprovisioning feature.
Migration Considerations
Following are migration considerations:
- Virtualized platform (Oracle VM) local repositories are not migrated. Any objects in the local repositories, such as VM or vdisks, must be backed up and manually migrated after the migration.
- Mount point for repositories (Oracle ACFS file system) is changed from
/u01/app/sharedrepo
to/u05/app/sharedrepo
. - VM templates are migrated as offline VMs. They can be used as
templates to clone VMs using the
command:
odacli clone-vm -n source_vm_name -cn cloned_vm_name
If not needed after the migration, then these VM templates can be deleted using the command
odacli delete-vm -n vm_name
. - CPU pools with odd number of cores are not migrated because CPU pools in KVM must have even number of cores. Manually create the CPU pools after migration and assign the CPU pools to the affected VM.
- The
net1
bridge on dom0, usually used as the public network on OVM andpriv1
, used as the private network for the ODA_BASE are not migrated to KVM vnetwork. - VM with attached VLAN without bridge is migrated as pubnet vnetwork.
- Manual customizations made directly in
vm.cfg
are not migrated. - By default, VM after migration uses virtio. Earlier Linux versions VM such as
Oracle Linux 5 which do not have the required virtio support fail to bootstrap
correctly. You can change the bus type from virtio to IDE, and then restart the
VM.
odacli modify-vm -n vm_name -dev bus=ide
To revert it back to the default virtio:odacli modify-vm -n vm_name -dev bus=virtio
This issue can also occur on Microsoft Windows VMs that do not have virtio installed.
- If migration fails while migrating any infrastructure resources
such as repo, cpu pool, vlan, vdisk and vmtemplate), the created resources are
reverted back. After the issue is fixed, rerun the command
odacli migrate-ovm2kvm
for migration. -
If migration fails while migrating VMs, the migration continues and an error is displayed when you run the command
odacli describe-ovm2kvm
for each failed VM migration. - After migration, the actual device name inside the VM could change. For example,
/dev/xvda
on the virtualized platform deployment could change to /dev/vda
after migration to KVM. If the device name, for example,/dev/xvda
is listed in/etc/fstab
inside the VM, then the VM can fail to start due to device name change after the migration. If the virtualized platform deployment uses the device name in/etc/fstab
, then rename with the label or UUID before migration. For more information about using label or UUID in the file system mount table, that is,/etc/fstab
, then refer to the Oracle Linux 7 Managing File Systems Guide at https://docs.oracle.com/en/operating-systems/oracle-linux/7/fsadmin/ol7-fsadmin.html#ol7-s1-fsadmin. - The network configuration of the VM could change after the migration. If you
cannot connect to the VM after migration, login to VM from the console using the
command
virsh console vm_name
and review and reconfigure the network, if necessary. The configuration steps are specific to the operating system. For details, refer to the operating system documentation. - Before migrating a Microsoft Windows VM, install the virtio driver for Windows. Refer to the My Oracle Support Note 2773840.1 Steps for MS Windows guests on ODA Bare Metal for the configuration procedure.
Steps in the Migration Process
- Run the
odaupgradeutil.sh
utility. - Reimage the appliance on both nodes.
- Run the command
odacli restore-node -g
to reprovision with Oracle Grid infrastructure andodacli restore-node -d
to reprovision the saved databases. - Run the
odacli migrate-ovm2kvm
command to migrate from virtualized platform to KVM. - Run the command
odacli describe-ovm2kvm
and examine the migration report for any errors. Fix the issues and then retry the operation.
Migrating from Virtualized Platform to KVM on Oracle Database Appliance
Understand the procedure to migrate from Virtualized Platform to KVM on Oracle Database Appliance.
WARNING:
Do not run cleanup.pl at any time during the migration process. That will erase all the Oracle ASM disk groups on the storage and you will not be able to reprovision your Oracle Database Appliance system with all the Oracle virtualized platform resources intact.Note:
After migration, the actual device name inside the VM could change. For example,/dev/xvda
on the virtualized platform deployment could change
to /dev/vda
after migration to KVM. If the device name, for
example, /dev/xvda
is listed in /etc/fstab
inside
the VM, then the VM can fail to start due to device name change after the migration.
If the virtualized platform deployment uses the device name in
/etc/fstab
, then rename with the label or UUID before
migration. For more information about using label or UUID in the file system mount
table, that is, /etc/fstab
, then refer to the Oracle Linux 7
Managing File Systems Guide at
https://docs.oracle.com/en/operating-systems/oracle-linux/7/fsadmin/ol7-fsadmin.html#ol7-s1-fsadmin.
Note:
Runodaupgradeutil
on ODA_BASE
at the first node (node0
) first. After
steps 3-5 complete successfully on node0
, run steps 3-5 on
ODA_BASE
at the second node (node1
).
Note:
You have completed migration of your databases from Oracle Database Appliance virtualized platform to the bare metal system. To migrate the databases from Oracle Database Appliance bare metal system to DB system, refer to My Oracle Support Note 2869506.1 at https://support.oracle.com/rs?type=doc&id=2869506.1.