How to Migrate Virtual Machines Between Proxmox Nodes

Easy guide to safely migrate virtual machines between Proxmox nodes. Our Proxmox Support team is ready to assist you. 

Migrate Virtual Machines Between Proxmox Nodes

Migrating virtual machines between Proxmox nodes helps optimize resources and maintain high availability. This guide explains the requirements, methods, and steps to move VMs smoothly, adjust settings, and ensure they run correctly on the new node.

How To Migrate Virtual Machines Between Proxmox Nodes

To migrate a virtual machine or Proxmox LXC Containers between nodes, open the Proxmox web interface and locate the VM or container in the resource tree. Right-click it and select “Migrate.” In the migration window, choose the target node and storage location, then initiate the migration. This process transfers the disks and memory to the new node, allowing the VM or container to resume with minimal downtime when performing a live migration.

System Requirements

Before migrating a virtual machine between Proxmox nodes, especially when running Proxmox VE on Raspberry Pi 5, it is crucial to verify that both the source and destination nodes meet all hardware, software, and network requirements. Ensuring these prerequisites are in place helps prevent compatibility issues, reduces downtime, and allows the migration of virtual machines and Proxmox LXC Containers to proceed smoothly and efficiently.

Hardware Requirements

• Compatible CPU architecture (Intel 64 or AMD64) with virtualization support (Intel VT/AMD-V or AMD-V)
• Minimum 2 GB RAM for the OS and Proxmox services, plus extra for guest VMs
• Adequate storage on the destination node, especially if not using shared storage

Software Requirements

• Compatible version of Proxmox Virtual Environment installed on all nodes
• All nodes joined to the same Proxmox cluster
• SSH access for advanced configuration and troubleshooting

Network and Access Requirements

• Stable network connectivity between nodes
• VM network settings compatible with the destination node
• Open firewall ports for cluster communication and data transfer
• Shared storage accessible by all nodes for live migration
• Proper user permissions on both source and destination nodes

Methods for Migrating Virtual Machines

Proxmox offers several ways to migrate virtual machines, each suitable for different scenarios depending on your setup and requirements.

Backup and Restore Method
This is the most straightforward approach. First, create a backup of the VM on the source node through the Proxmox web interface or CLI. If the backup storage is not accessible from the target node, transfer the backup file using tools like scp or rsync. Finally, restore the VM on the destination node using the web interface or the qmrestore command. This method ensures your data is preserved and is suitable for most migration needs.

Using Rsync to Transfer Configurations
Rsync allows you to move VM configurations and disk images between nodes efficiently. Begin by shutting down the VM on the source node. Then use rsync to copy the configuration files and disk images to the target node. After transfer, update paths and register the VM if needed. This method is useful when precise control over files is required, especially in non-clustered setups.

Remote Migration with qm Command
For advanced users or non-clustered environments, the qm remote-migrate command provides a direct way to migrate VMs over SSH. Ensure the target node has sufficient CPU, memory, and storage. Specify the VMID, target host details, storage, and network bridge in the command. After migration, verify that the VM is running correctly on the new node. This method reduces downtime and is effective for large-scale migrations.

Step-by-Step Guide to Migrating VMs

1: Prepare the Environment

• Ensure both source and destination nodes are part of the same Proxmox cluster.
• Verify network connectivity between nodes.
• Confirm the destination node has sufficient CPU, RAM, and storage for the VM.
• If performing live migration, ensure shared storage is accessible from both nodes.

2: Back Up the Virtual Machine

• • Open the Proxmox web interface on the source node.
  • Select the VM you want to migrate.
  • Click Backup and choose a storage location (local, network storage, or Proxmox Backup Server).

• Start the backup process and wait until it completes.

3: Transfer Backup (if not using shared storage)

• If the backup storage is not shared, copy the backup file to the destination node using scp or rsync.

4: Restore the VM on the Target Node

• On the destination node, open the Proxmox web interface.
• Click Restore, select the backup file, assign a new VMID if necessary, and choose the target storage.
• Start the restore process and wait until it completes.

5: Adjust Network and Configuration

• Check the VM’s network settings and adjust for compatibility with the new node.
• Verify CPU and memory allocation matches the VM’s requirements.
• Update storage paths if they differ from the source node.

6: Start and Verify the VM

• Power on the VM on the destination node.
• Access the VM and ensure all services and applications are running correctly.
• Check connectivity and performance to confirm successful migration.

Tips for Smooth Migration

To ensure a smooth migration of virtual machines, use live migration whenever possible and leverage shared storage to minimize downtime, while confirming that the target node has sufficient CPU, RAM, and storage resources. After migration, verify that the VM is running correctly on the destination node, test network connectivity, access applications, and check disk and data integrity. If issues arise, review network configurations and firewall rules, confirm storage availability, examine the VM state, and consult Proxmox logs for error messages. Additionally, ensure API token permissions and replication settings are correctly configured to avoid migration conflicts.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion 

Proper planning and execution allow you to efficiently Migrate Virtual Machines Between Proxmox Nodes with minimal downtime and smooth performance.

In brief, our Support Experts demonstrated how to fix the “554 5.7.1 : Relay access denied” error.