OCI OEM Installation – (Using Market Place Image)
Introduction Monitoring plays a major part in mission-critical environments. Most businesses depend on IT infrastructure. As the ... Read More
RackWare – Workload Migration (RMM) – Part 1
Migrating Application and Database Servers from on-prem to Cloud is really challenging. Current era organizations are focusing to stretch towards Clouds to optimize their workloads. This gives immense pressure on IT Architects and administrators on how swiftly and smoothly they can migrate servers to the Cloud.
After the migration, the next challenge is to have an optimal DR (Disaster Recovery) Strategy. The best practice would be replicating the servers to different regions. There are many tools in the market to address these challenges,
RMM is a great tool to address migrations and DR strategies.
Product Overview
RackWare Migration Manager (RMM) is a third-party application that we employ as a Cloud Migration and Disaster Recovery solution. RMM is compatible with all of the major cloud providers including Oracle, Microsoft Azure, Amazon Web Services (AWS), and Google Cloud, and can also be used in On-premise scenarios.
The product consists of the following areas :
- Discovery and Analysis
- Workload Migration
- Disaster Recovery and Backup
When organizations are planning to move their current VMware, Hyper-V, or Oracle VM to the cloud, RackWare is a really good solution to cater to this environment. This migration methodology in addressing migration at the VM level.
The following figures illustrate the RackWare Technology Support matrix:
At a high level, the RackWare CloudMotion process consists of:
- Provisioning of the RackWare RMM Instance
- Setup network ingress and egress rules allowing communication between source and target networks.
- Initialize and license the RMM Server then start the RMM Service
- Configuring SSH connectivity between the source and the target server
- Create Cloud User and Policies
- Create and configure a ‘Wave’ within the RackWare Admin UI (User Interface)
Note: If we are planning to use the same IP Address Subnets on the source and target networks we will require a bridge network. The following is a link to RackWare documentation outlining the above process in greater detail.
This figure illustrates how the RackWare Bridge provides the IP Aliasing.
Simplified diagram of the RRM to Bridge Server communication:
RackWare has different feature sets, unlocked via licensing options:
- RackWare Migration Manager
- RackWare Migration Manager (RMM) BYOL
- RackWare Disaster Recovery (SMB)
As a partner, to obtain licensing for POC purposes we can email licensing@rackwareinc.com to obtain a 30 day trial license.
Deployment Scenarios
There are 3 ways to deploy the RMM software
- Install the software from the yum package to RedHat Linux and derivative operating systems (eg Oracle Linux and CentOS).
- Import image from OCI block storage
3. Provisioning from an OCI Marketplace image
In this article, we covered only product overview and deployment methods. Next article we will cover the installation and configuration part of the RMM server.
More from this Author
OCI Tablespace Creation Error – ORA-28361: Master Key not yet set for CREATE TABLESPACE in OCI DBCS
Introduction We are living in a data era. Every organization invests in a colossal sum of money to secure its IT infrastructure environment. ... Read More
