Virtual Machines that have been specifically selected to migrate to OCI within the OCM UI

The entire on-premises environment that is subject to discovery and analysis by OCM

Virtual Machines that have been automatically discovered and listed in the OCM UI

An OCI Compute instance representing the migrated on-premises asset in the OCM UI

When a private container registry is required for internal use, and the need to store, share, and manage container images is prioritized

When there is a need for a managed container orchestration service for automatic scaling, upgrades, and security patching

When there is a need to store, share, and manage container images with a highly available and scalable architecture

When there is a need for a platform with serverless capabilities to efficiently run containerized workloads

To create a backup from the existing Migration Plan, as a precautionary measure against misconfiguration

To validate different compute shapes for each VM ensuring the most effective configuration can be chosen

To incrementally increase the allocated budget for each Migration Plan

To accelerate the migration task by assigning each Migration Plan to the respective migration team

A Compute instance is automatically launched after the replication process

Deploy a Resource Manager Stack to launch the Compute instance with the replicated Block Volume

Create a Compute instance with an attached Block Volume and configure the Hydration Agent to transfer the replicated data into the Block Volume

HCX Bulk Migration for migrating business-critical VMs and HCX vMotion for non-critical dev-test VMs

HCX vMotion for migrating business-critical VMs, and Cold Migrations for non-critical dev-test VMs

Cold Migration for migrating both business-critical and non-critical dev-test VMs

HCX Bulk Migration for migrating the business-critical VMs, and Cold Migrations for non-critical dev-test VMs

The replication plugin does not support encrypted VM disk files

The OCI tenancy has exceeded its service limit for compute instances, preventing the replication plugin from provisioning necessary resources

The source VMs are using an unsupported file system that the replication plugin is unable to process

The VDDK (Virtual Disk Development Kit) file required by the replication plugin is missing inthe OCI Object Storage

Oracle Golden Gate

Oracle Enterprise Manager Migration Workbench

OCI Database Migration

Oracle SQL Developer

Snowball

Data Transfer Service

Data Integration

Storage Gateway

Serverless

Base Database

Exadata Database on Dedicated Infrastructure

Dedicated Exadata Infrastructure

You can run a cloud premigration advisor tool to perform compatibility check prior to migration

During physical migration, copies of database objects are created in dumps

Source and Target database versions must be the same

You cannot filter and migrate database objects

You cannot achieve zero or near-zero downtime with physical migration

Is an agent software installed on the on-premises VMs to trigger replications into OCI

Is a temporary compute instance automatically provisioned and terminated during the migration process

Is responsible for copying the replicated data into OCI Block Volumes

Represents the migrated VM in OCI compute

To automate data replication between OCI compute instances

To transfer data between OCI regions

To transfer data between different OCI Compartments

To prepare transfer disks for data shipment to Oracle

Virtualization offers more flexibility in terms of application dependencies

Virtualization maximizes efficiency by running multiple applications on the same OS kernel

Containers require a full operating system to run, whereas virtual machines share a single operating system

Containerization allows for more efficient utilization of hardware resources by sharing the host operating system