Guide · Agentless VM migration

What agentless VM migration is

Z-Move, the agentless VM migration platform, moves virtual machines between Zadara, AWS and Azure without installing anything inside them. It works from outside the VM, through the cloud APIs: snapshots, volumes and temporary workers that it creates and removes itself.

Agentless, in practice

  • Nothing is installed in your VMs, and nobody logs in to them.
  • No password of the guest operating system is needed: only cloud access keys.
  • The source VM is never stopped or changed. Rolling back means carrying on with it.
  • A test VM has to answer on SSH, RDP, HTTPS or HTTP before you switch.
  • Temporary workers, snapshots and volumes are removed at the end, and the session lists them.

Agent-based and agentless, side by side

An agent-based tool installs a small program in the operating system of every server to move. The agent reads the disks from inside and sends them to the destination, often continuously, so the copy stays close to the source until the cutover. It needs access to each server, a change window to install the agent, outbound network rules from every server, and the agent removed afterwards.

An agentless tool never enters the VM. It asks the cloud for a snapshot of each disk, reads that snapshot with machines of its own and writes the disks in the destination cloud. The VM keeps running as it was, and the operating system never knows.

The trade-off, stated plainly

A snapshot is crash-consistent: the disks are copied as they were at one instant, like a server after a power cut. Most systems start cleanly from that. For a database or an application that writes a lot, stop the application or the VM before the snapshot; the downtime is then the copy time of that VM.

Agent-based tools can keep a copy in sync until the last minute, at the price of software on every server. Between Zadara regions, Z-Move offers the same idea without an agent: Replication keeps a standby VM in another region refreshed every 30 minutes up to every 24 hours, with failover from the dashboard.

How Z-Move does it

  1. You pick the source and the destination and add the cloud access keys of both. Keys are encrypted and deleted 30 days after the job ends.
  2. You choose the VMs, or a snapshot or an image. Pre-checks confirm the credentials, the disks, the operating system, the image name and recent quota errors before anything starts.
  3. Z-Move takes a snapshot of each disk through the cloud API. On AWS it creates an image of the instance without rebooting it; on Azure it snapshots each disk and reads it through a temporary access link.
  4. Temporary workers in the clouds read the snapshots and write the disks in the destination, over TLS. On the routes through the Z-Move relay the disks stream through memory and are never written to disk on the way; Azure routes go straight between the clouds.
  5. When the destination needs it, the operating system is adapted: Linux VMs from Azure get their cloud-init, network (netplan), Azure agent and fstab changed for Zadara, in seconds.
  6. The destination gets an image ready to launch (or a managed disk on Azure), and every temporary resource is deleted.
Session resources after the migration: workers terminated, snapshots and volumes deleted, image created.
Session resources · web-01 · temporary resources removed

The boot test is the proof

Copying disks is half the job. From the job page, a boot test starts a VM from the new image in the destination and checks it for up to 8 minutes. It passes when the system accepts a connection on SSH, RDP, HTTPS or HTTP, or when the console shows it booted from its own disk. When neither happens, the result says why, or says that it is inconclusive instead of guessing.

The test VM and its temporary public IP are always removed at the end. On Azure, the test boots a copy of the managed disk in a network of its own, and removes the copy, the VM and the network at the end.

Z-Move session page for a completed Azure to Zadara migration: 39.7 MB/s on average, boot test passed with SSH on port 22, 19m 40s in total.
Timings from a real Azure East US → Zadara run (30 GiB). Names from the demo environment.

What Z-Move creates in your cloud account

  • Temporary worker VMs, tagged as Z-Move workers, terminated when the job ends. A sweep every 10 minutes terminates any worker left behind, after checking its tags.
  • Snapshots and volumes for the copy. The snapshots Z-Move creates are deleted after a completed migration; snapshots and images you choose as the source are never deleted.
  • A security group for the workers, which lets in only the Z-Move server and stays for the next migrations.
  • Temporary public IPs for the workers and the boot test, released at the end.

Routes

Each route has its own guide, with a measured run and what to check before the switch:

FAQ

Agentless migration: questions

Something else? Write to hello [at] zmove.click

Do I need the password or SSH key of my VMs?

No. Z-Move works with snapshots and volumes through the cloud APIs, with the access keys of the clouds. It never logs in to your VMs.

Does the VM have to be stopped?

No. The copy is crash-consistent. For databases and other applications that write a lot, stop the application or the VM before the job to get a consistent copy.

Is an agentless copy slower?

Speed depends on the route and on how fast the source cloud serves the snapshot, not on the method. Our measured runs went from about 12 MB/s on AWS sources to 166 MB/s uploading to Azure, and each route guide shows its own run.

Does it work with Windows?

Yes. Disks are copied block by block, so the system moves as it is. On a Zadara destination, check that the image has the VirtIO drivers before the switch; the pre-checks warn you about them.

Can I keep a standby copy instead of migrating once?

Between Zadara regions, yes. Replication keeps a standby VM in sync every 30 minutes up to every 24 hours, with failover from the dashboard.

What is left in my account afterwards?

The image or disk you asked for, and the workers' security group for the next migrations. Workers, temporary volumes, test VMs and the snapshots Z-Move created are deleted, and the session lists each one.

Demo

See a full run, from wizard to boot test.

Book a demo and follow a complete migration: wizard, pre-checks, live session, boot test and cleanup.

Or write to hello [at] zmove.click

We only use these details to reply to you.