Route · Zadara → Zadara

Migrate VMs between Zadara regions

Z-Move, the agentless VM migration platform, moves VMs from one Zadara region to another, across continents too, and checks that they boot in the destination. Nothing is installed in your VMs, and they keep running during the copy. The same platform keeps a standby VM in sync in another region and exports VMs to files.

At a glance

The route, measured

Zadara → Zadara

In production
How it runs

Relay. An export worker reads the source, an import worker writes the destination, and the disks stream between them in memory, over TLS.

You get

An image in the destination region, ready to launch.

Operating system

Nothing to adapt: the same platform on both sides.

Measured run
21 GB2 disks
6m 44sto transfer
53 MB/saverage speed

Production firewall VM, moved between two Zadara regions. In another measured run between two Zadara regions, a 30 GiB VM took 15.6 minutes from start to finish, with the transfer at 60 MB/s and the network as the bottleneck.

Boot test
Available. The test VM has to answer on SSH, RDP, HTTPS or HTTP.

How a migration between Zadara regions runs

  1. Add the keys of the source and the destination regions, or paste a zCompute endpoint that is not in the list. Keys are encrypted and deleted 30 days after the job ends.
  2. Pick the VMs, or a snapshot or an image. Several VMs run as a batch, one job each, into the same destination region.
  3. Pre-checks confirm the credentials, the disks, the operating system, the image name and recent quota errors before anything starts.
  4. Z-Move creates an image of the VM without rebooting it, which takes a snapshot of every disk. An export worker in the source region streams the disks over TLS, through the Z-Move relay, to an import worker already waiting in the destination. The data passes through memory and is never written to disk on the way.
  5. The import worker writes the volumes, snapshots them and registers the image. The workers and the temporary volumes are deleted, the source snapshots Z-Move created are removed after a completed migration, 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 the destination. It passes when the system answers on SSH, RDP, HTTPS or HTTP.
Live session: 99.2 of 220 GiB copied at 97.6 MB/s, three disks in parallel, network as the bottleneck.
Live session · erp-db · 3 disks in parallel

Nothing to adapt, at any distance

Both sides run the same platform, so the system moves as it is: no drivers to add and no settings to change.

Migrations between continents have been validated, for example from Brazil to Nigeria. Z-Move runs in production at a telecom operator: 380+ migrations, 94% of them completed.

Keep a standby in another region

Replication keeps a standby copy of a VM in another Zadara region, refreshed on a schedule. Each refresh is a migration of its own: a new standby starts from that copy's image, takes over the public IP and replaces the previous one. Replication runs in production today.

  • Every 30 minutes, every hour, every 6 hours or every 24 hours, and you can change the interval later.
  • After 3 failed refreshes in a row, replication pauses until you resume it.
  • Failover from the dashboard stops the schedule and gives you the standby's connection details. From then on the standby is never overwritten.
  • Zadara to Zadara only.

Export a VM to a file

Export writes the disks of a Zadara VM as qcow2 or VHD files into an S3 bucket you own, such as AWS S3 or another S3-compatible store. Z-Move never keeps the files. Z-Move does not bill exports by the GiB today; what an export costs depends on your providers (the data leaving the Zadara region and the storage in your bucket), so it varies.

  • You register a bucket once and reuse it. Z-Move checks the connection when you save it and again when an export starts.
  • The export page shows each step, the progress of the disk being converted or sent, and the totals at the end.
  • The download link is signed with your own bucket credentials and lasts 24 hours by default.

Cutover, 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. For shorter windows, keep a standby with replication.

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

Before you move traffic, check what stays in the source region:

  • Floating IPs and security groups belong to the source region: recreate in the destination what the VM needs.
  • IP addresses change: update DNS records, allow-lists and anything else that points at the old addresses.
  • Only the volumes attached to the VM when the job starts are copied.

What it costs

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

The temporary workers, volumes and snapshots run in your own Zadara projects while the job lasts, and are deleted at the end.

Security

The workers carry no secrets of the platform. Each starts with only a token valid for its own job, receives the access key for its side over TLS while the job runs, keeps it in memory, and accepts no connections from the internet. Keys are encrypted at rest and never written to logs. Because the key reaches the worker, the permissions you give it are the real limit: give it only what the migration needs (see the questions below).

See the security overview, the DPA and the subprocessors.

FAQ

Zadara to Zadara: questions

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

Can I move VMs between regions on different continents?

Yes. Migrations between continents have been validated, for example from Brazil to Nigeria. The disks travel over TLS through the Z-Move relay.

Can I use a zCompute endpoint that is not in the list?

Yes. Choose "+ Other endpoint" in the region list and paste the HTTPS URL of the zCompute endpoint, for example a dedicated deployment. It works for the source and for the destination.

Do I have to change anything in the operating system?

No. Both regions run the same platform, so Linux and Windows move as they are, with nothing to adapt.

Can I keep a standby instead of moving once?

Yes. Replication keeps a standby VM in another Zadara region, refreshed every 30 minutes, hour, 6 hours or 24 hours. Each refresh starts a new standby from the latest copy and moves the public IP to it. It runs in production today.

What happens when I fail over?

The schedule stops and the dashboard gives you the standby's connection details. The standby is never overwritten after that, so it stays as it was at the last refresh.

Can I export a VM to a file instead?

Yes. Export writes the VM's disks as qcow2 or VHD files into an S3 bucket you own, and gives you a download link signed with your own credentials. It works from Zadara sources.

What does the Zadara key need?

Our guidance: a dedicated user with the Member role only in the projects involved, and the AmazonEC2FullAccess policy in those projects. Z-Move creates and deletes volumes, snapshots, images, instances, a security group and floating IPs, so read-only policies are not enough. Tenant admin is not needed.

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.