Route · Azure → Zadara

Migrate VMs from Azure to Zadara

Z-Move, the agentless VM migration platform, copies the disks of your Azure VMs into a Zadara region, adapts Linux so it starts there with network, registers an image ready to launch and starts a test VM that has to answer on SSH or RDP. Nothing is installed in your VMs, and they keep running during the copy.

At a glance

The route, measured

Azure → Zadara

In production
How it runs

Direct. One worker in Zadara reads the Azure snapshot itself, with nothing in the middle.

You get

A Zadara image, with the system already adapted.

Operating system

Adapted automatically in 3 s: cloud-init, network (netplan), Azure agent and fstab.

Measured run
30 GiB1 disk
19m 40stotal time
39.7 MB/saverage speed

Validation run, Azure East US to Zadara, Ubuntu 24.04. Azure set the pace: the worker reads each disk in parallel streams and picks a stream up where it stopped when the connection drops. The Linux adaptation took 3 seconds.

Boot test
Passed: SSH answered in 2m 28s.

How an Azure to Zadara migration runs

  1. Add an Azure service principal for the source (subscription ID, tenant ID, client ID and client secret) and the keys of the Zadara region. They are encrypted and deleted 30 days after the job ends.
  2. Pick the Azure VMs. Each VM runs as its own job, into the same Zadara region.
  3. Pre-checks confirm the credentials, the disks, the operating system, the image name and recent quota errors before anything starts. A Windows VM gets a warning about the VirtIO drivers that Zadara uses.
  4. Z-Move snapshots each disk in Azure and starts one temporary worker in the Zadara region. The worker reads the snapshots straight from Azure, through a temporary read-only link to each one, in parallel streams, and writes them to Zadara volumes. There is no relay and nothing in the middle.
  5. Z-Move adapts the Linux system disk for Zadara (see below), snapshots the volumes and registers the image. The Azure snapshots and the worker are deleted, and the session lists every resource it created and removed.
  6. From the job page, a boot test starts a VM from the new image in Zadara. It passes when the system answers on SSH, RDP, HTTPS or HTTP.
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.

Linux adapted for Zadara, in seconds

A Linux VM created in Azure starts on Zadara, but its configuration only works in Azure: cloud-init waits for Azure's provisioning, the network is tied to the Azure network card, and the Azure agent keeps looking for Azure. Left as it is, the VM comes up without network.

So before the image is made, Z-Move changes the system disk:

  • cloud-init gets a list of data sources without Azure, so it detects the platform it runs on.
  • Network: DHCP on any Ethernet card, through netplan or, on distributions without netplan, a NetworkManager profile.
  • The Azure agent is taken out of the boot.
  • The Azure temporary disk is commented out in /etc/fstab, and a copy of the original file is kept.

What stays as it is

The original files are not changed: the new settings sit in files of their own. The adaptation is best effort: if it fails, the session log says so and the disk moves as it came. In the measured run it took 3 seconds, and the boot test passed with SSH answering on port 22.

Windows disks, a root file system on LVM and data disks are copied as they are, without adaptation. For Windows, make sure the VM has the VirtIO drivers that Zadara uses before the switch.

Before you switch

The image carries the disks. What belongs to the Azure subscription stays there, so check these before you move traffic:

  • Network security groups, public IP addresses and load balancers: recreate in the Zadara region what the VM needs.
  • Managed identities: applications that call Azure services with the VM's identity need credentials of their own on Zadara.
  • IP addresses change: update DNS records, allow-lists and anything else that points at the old addresses.
  • Only the disks attached to the VM when the job starts are copied. The Azure temporary disk is not one of them.

Downtime and rollback

Z-Move copies a snapshot, so the VM keeps running and is never stopped or changed. The copy is crash-consistent, like a server after a power cut. For a database or a busy application, stop the application or the VM before you launch the job: the downtime is then the copy time of that VM.

Rolling back means carrying on with the Azure VM, which stays untouched until you decide to retire it.

What it costs

Z-Move bills US$0.05 per GiB written to Zadara: the data, not the size of the disk. A retry does not pay again for disks already copied.

On your Azure bill, during the job: the snapshots of the disks and the data that leaves Azure. The snapshots are deleted at the end. The temporary worker runs in your Zadara region.

Security

The worker carries no secrets of the platform. It starts with only a token valid for its own job, receives the credentials it needs over TLS while the job runs, keeps them in memory, and accepts no connections from the internet. Credentials are encrypted at rest and never written to logs.

On this route the data goes straight from Azure to your Zadara region and does not pass through the Z-Move servers.

See the security overview, the DPA and the subprocessors.

FAQ

Azure to Zadara: questions

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

Do I need to install anything in my Azure VMs?

No. Z-Move snapshots each disk through the Azure API, and a temporary worker in Zadara reads the snapshots. Nothing is installed in the VM, and the VM is never stopped or changed.

Does my data pass through the Z-Move servers?

No. On this route the worker in your Zadara region reads the snapshots straight from Azure. With a private deployment, the platform itself also runs in your own infrastructure.

Will the VM have network on Zadara?

Yes, for Linux: Z-Move adds DHCP on any Ethernet card and removes the dependence on Azure's provisioning. In the measured run, SSH answered on Zadara 2m 28s after the boot test started.

Does it work with Windows?

Windows disks are copied as they are, without the Linux adaptation. Check that the VM has the VirtIO drivers that Zadara uses before the switch; the pre-checks warn you. Windows VMs have already been migrated on the Azure routes.

What does the Azure service principal need?

Read access to the subscription, its resource groups and the VMs, and the right to create, read, export and delete snapshots in the resource groups of the source disks. The tightest option is a custom role on those resource groups; the simpler one is the built-in Contributor role on those resource groups only, never on the whole subscription.

What happens to the snapshots in Azure?

Z-Move creates one snapshot per disk to read from, and the worker deletes them at the end of the job. Your disks and any snapshots you made yourself are never touched.

How long does it take?

It depends on the data and on how fast Azure serves it. In a measured run, a 30 GiB Ubuntu 24.04 VM took 19m 40s from start to finish, at 39.7 MB/s on average, and SSH answered on Zadara 2m 28s after the boot test started.

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.