Classic bare metal to bare metal or virtual server on VPC migration

In this migration process, migrating happens from a physical bare metal server to a bare metal or virtual server instance. The RMM tool simplifies the overall migration process of moving the OS, applications, and data from the bare metal environment to a bare metal or virtual server. You might want to move away from bare metal servers due to their hardware lifecycle (qualifying new hardware, OS certification, and EOL support) or due to data center closures. You can modernize your environment and adopt virtualization by migrating from bare metal servers to bare metal or virtual servers.

Planning for your migration

Before you begin migrating your physical bare metal server to a virtual server, review the following requirements:

You need an existing VPC environment.
You need to install an RMM SSH key on both the source and target environments. Windows needs to install the SSH Daemon provided by the RMM server.
Your bare metal server boot volume needs to be less than 250 GB.
Your bare metal server needs to be on a supported operating system. For a list of supported operating systems, see Virtual server images.
Your source and target need to be able to reach each other and the RMM. You can establish connectivity over the public internet with public IP addresses. If you have a private-only environment, then you must set up either a VPN or transit gateway, use the following links:

To improve data transfer rate, adjust bandwidth allocation of RMM server. To know how to change bandwidth allocation, see Adjusting bandwidth allocation by using the UI.

Migration considerations

Capabilities

Application and environmental settings are preserved
Data sync (data drift) before final cut-over is supported
Data migration (secondary and block volume)

VPC does not have support for snapshot, replication, and shared volume. You can manage these solutions through the native OS capabilities, tools, or third party of your choice.

Limitations

New IP address (original IP is not preserved).
Classic add-ons are not carried over.
File-based storage migration is not supported.
Hardware configuration is not brought over (RAID configuration).
Bare metal with GPU is not supported due to no GPU support on VPC.
Not an OS replatforming (Windows to Linux or vice versa, changing linux distribution, or major software upgrade). Software upgrades must be handled through the normal process.

Validating your migration

After your server migration, validate your compute resources, such as applications and data. Check the following items:

Validate or update your FQDN/Hostname.
Update your yum repos, application settings, and configuration file.
Update licensing where applicable.
Remove RMM SSH key from target after final validation.