lift and shift ebs to oci using cloud manager

 Lift and Shift ebs to OCI is an approach, one among many for migrating your on Premises Oracle EBS to Oracle Cloud Infrastructure. In this post, i will try to explain the steps on how we can lift and shift ebs to oci using cloud manager. It is already assumed that cloud manager is already configured to be used for your environment. You can check my previous post https://samappsdba.blogspot.com/2021/01/step-by-step-configure-ebs-cloud-manager.html on how we can configure ebs cloud manager in oracle cloud infrastructure. 

I have followed the traditional approach of lift and shift of on premise EBS to Oracle Cloud. There is an another approach now in the latest version of Cloud manager where you can create a standby environment in OCI and later promote it to primary after sync. In the traditional method, the first step would be prepare the environment and installing the backup module.

Source Environment Requirements

 Note:-My target DB will be in compute and the below listed patches are for database running on  compute only. 

Source database should be in archive log mode

Check if ntp service is configured

In the apps tier, AD/TXK should have minimum level 11 and should have the below patches    applied in application tier and database tier respectively

Patch 28371446:R12.TXK.C

Patch 29965377:R12.TXK.C

Patch 30601878:R12.TXK.C

Patch 30713114:R12.TXK.C

Patch 31314595:R12.TXK.C

database patches-31113249

Generating API Signing Key:-

 [oracle@apps ~]$ mkdir ~/.oci

Generate private key

[oracle@apps ~]$ openssl genrsa -out ~/.oci/oci_api_key.pem 2048

Generating RSA private key, 2048 bit long modulus

...........................+++

..............................................................................+++

e is 65537 (0x10001)

Generate public key

[oracle@apps ~]$ openssl rsa -pubout -in ~/.oci/oci_api_key.pem -out ~/.oci/oci_api_key_public.pem

writing RSA key

get the fingerprint:-

[oracle@apps ~]$ openssl rsa -pubout -outform DER -in ~/.oci/oci_api_key.pem | openssl md5 -c

writing RSA key

(stdin)= c6:2e:e1:d0:78:53:13:87:93:15:4a:85:6e:13:96:70

[oracle@apps ~]$

Upload the public key to the user's api signing key in OCI console.

Note: The user which you select should have the privileges to create resources in the compartments.

Note:-On the application tier server and the database tier server, the SSH configuration files (~/.ssh/config) must have the entry "ServerAliveInterval 100—under root server

Using the backup, we will now provision a new EBS instance in OCI

We will use the advance provisioning.

In this section, password validation will be done. If there are any validation issues, errors will be displayed. Correct the passwords and click Next to proceed. 

Select the Cloud Database Service option for your environment, either Compute, Virtual Machine DB System, or Exadata DB System. I had choosen Compute.

Click Next to enter the application details:-

A new feature has been added which is Zone. You can now segregate the instance as internal and external zones. We can have a load balancer shared between multiple zones of the same type. This configuration allows for two separate URLs to resolve to the same IP address and the shared load balancer will target one backend set or another.

 

Define the internal zone

In the Web Entry Point region, Choose one of the following: New Load Balancer (LBaaS), Manually Configured Load Balancer to select a manually deployed existing load balancer, or Application Tier Node to choose the primary application tier as the entry point.

If we choose New load balancer or manually configured load balancer option and file system as shared, then going forward, using Cloud manager we can add a secondary node using the "ADD Node"  

 

We can click on add here and add a secondary node if we want and click on save zone

Click next

In this section, you want CM to perform any additional tasks, you can specify in this sestion.

click next and add the ssh keys and click next.

Once the provisioning is complete, we can see the details under Environment section in Cloud Manager

There is a new feature added in this new version of Cloud manager of assigning backup policies.

Access the EBS Environment page now

If DNS is not in place, make a modification to the local /etc/hosts file and add the required ingress rules in the subnet security lists.

In the mentioned post, i have tried to demonstrate how we can lift and shift EBS 12.2 from on premise to OCI using traditional method. It wasn't a straightforward method as i had faced many challenges. I have  written a separate post https://samappsdba.blogspot.com/2021/01/oracle-e-business-suite-cloud-manager-compute-instance-configuration-issues.html on the issues encountered and it will be updated regularly as and when i encounter new issues.  Hope this post helps someone. Happy learning Cloud and EBS..:)

The complete step by step document is available at a price of $45. If you need it, please contact me over samratsinha05@gmail.com or Whatsapp at +91-8709658491

References:-https://docs.oracle.com/cd/E26401_01/doc.122/f35809/toc.htm