Migrating applications and Database Servers from on-prem to the Cloud is really challenging. Current-era organizations are focusing on stretching towards Clouds to optimize their workloads. This puts immense pressure on IT Architects and administrators to migrate servers swiftly and smoothly to the Cloud.
After the migration, the next challenge is to have an optimal DR (Disaster Recovery) Strategy. The best practice is to replicate the servers to different regions. Many tools are available to address these challenges, but RMM is a great tool for 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. This migration methodology addresses 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
- Set up 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)
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, we can email licensing@rackwareinc.com to obtain a 30-day trial license for POC purposes.
Deployment Scenarios