Measured runs

How long does a VM migration take? Measured runs between Zadara, AWS and Azure

Z-Move, the agentless VM migration platform, times every phase of every migration. These are our measured runs between Zadara, AWS and Azure: how long each one took, where the time went and what set the speed, so you can estimate your own cutover.

The short answer

In our measured runs, a VM with 8 to 30 GiB of disk moved in 9 to 21 minutes from start to finish. Most of that time is not the copy: starting the temporary workers and registering the image take a few fixed minutes, whatever the size of the VM.

  • AWS → Zadara: 8 GiB in 17m 08s; 19 GiB on two disks in 20m 29s.
  • Zadara → AWS: 20 GiB in 14m 12s, with the transfer at 71.4 MB/s.
  • Azure → Zadara: 30 GiB in 19m 40s, including the Linux adaptation, which took 3 s.
  • Zadara → Azure: a 20 GiB disk in 9m 07s, because only the 2.3 GiB that held data were sent.
  • Zadara → Zadara: 30 GiB in 15.6 minutes, with 8.5 minutes of transfer at 60 MB/s on a mostly empty disk.

Read these numbers with care

Each figure is a single run, on one pair of regions, in our test environment. Your times depend on how much data the disks hold, how many disks there are and the network between the two regions. Z-Move also runs in production at a telecom operator, with 380+ migrations, but the runs above are the ones we measured phase by phase.

Where the time goes

Every Z-Move session records its phases. Three sessions show the pattern:

  • Zadara → Azure, 20 GiB, 9m 07s: starting the worker 5m 59s (65.8%), preparing the source 46s, waiting for the target worker 10s, copying 2m 04s (22.7%), registering the result 7s.
  • Zadara → AWS, 20 GiB, 14m 12s: starting the worker 5m 03s (35.2%), preparing the source 1m 14s, waiting for the target worker 24s, copying 4m 47s (33.3%), snapshot and image registration 2m 44s (19.1%), cleanup 9s.
  • AWS → Zadara, 19 GiB on two disks, 20m 29s: queue and preparation 3m 40s (17.9%), export 49s, and the import 15m 58s (77.9%), at 19.3 MB/s on average since the export started.
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.

The fixed part

Starting the temporary workers took between 2 and 6 minutes in these runs. Z-Move starts the import worker in the destination at the same time as the export worker in the source, so the two boots overlap instead of adding up.

Registering the result takes from a few seconds to a few minutes. On AWS, finishing the snapshot behind a new image took about 2.5 minutes. If you run the boot test, add the time the new system takes to answer: SSH answered in 1m 21s after AWS → Zadara and in 2m 28s after Azure → Zadara.

What sets the speed on each route

  • AWS as the source: a volume made from an EBS snapshot is loaded from Amazon S3 the first time each block is read, by a single stream. The source set the pace in our runs: 12.4 MB/s for 8 GiB, and 19.3 MB/s on average for 19 GiB on two disks.
  • Zadara → AWS: the network between the regions was the limit, at 71.4 MB/s with no reconnects.
  • Azure → Zadara: a worker in Zadara reads the Azure snapshot itself, with parallel reads. The first runs went through the relay at about 5 MB/s (30 GiB in 1h 43m); the direct path brought the same size to about 20 minutes, at 39.4 MB/s, recovering 116 dropped connections on the way.
  • Zadara → Azure: only the parts of each disk that hold data are sent. A 20 GiB disk with 2.3 GiB of data went through in 2m 04s, at 165.3 MB/s.
  • Zadara → Zadara: empty blocks are skipped, so a mostly empty 30 GiB disk moved at 60 MB/s; the network between the regions was the limit.

Estimate your own migration

A rough estimate is a fixed part plus the data divided by the speed of your route. In the runs above, the fixed part (starting the workers, preparing the source and registering the result) was about 7 to 10 minutes.

An example, as an estimate only: a VM with 100 GiB of data going from Zadara to AWS at the 71.4 MB/s we measured needs about 25 minutes of transfer, so roughly 35 minutes in all. The same 100 GiB coming from AWS at 12.4 to 19.3 MB/s needs about 1h 30m to 2h 25m of transfer, because of the way EBS loads snapshot data.

The best estimate is your own: migrate one representative VM first. Its session page shows each phase, the speed and what held it back.

How to shorten the downtime

  • The source keeps running during the copy, because Z-Move copies a snapshot. Stop the application only when you need a consistent copy of a database or a busy application: the downtime is then the copy time of that VM.
  • The disks of one VM are copied in parallel. Several VMs selected together run as one job each, one after another, so plan the window VM by VM.
  • Run the boot test before the switch, not during it, so the cutover is only the change of traffic.
  • Between Zadara regions, replication keeps a standby up to date, every 30 minutes up to every 24 hours, for windows shorter than a full copy.

FAQ

Migration time: questions

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

Why does a small VM still take more than ten minutes?

Part of every migration is fixed: starting the temporary workers took 2 to 6 minutes in our runs, plus preparing the source and registering the image. For a small disk, that fixed part is most of the session.

Does the time depend on the size of the disk or on the data?

Mostly on the data. Empty blocks are skipped, and to Azure only the parts that hold data are sent: a 20 GiB disk with 2.3 GiB of data took 2m 04s to copy. Billing follows the data as well, not the size of the disk.

Does the VM stop while it is copied?

No. Z-Move copies a snapshot through the cloud APIs, so the source keeps running and is never changed.

Can I see where the time went in my own migration?

Yes. Each session shows its phases with their times, the speed, the time left, the reconnects and what held it back, for example the source or the network.

Why was the first Azure → Zadara run so slow?

It went through the relay, at about 5 MB/s. Z-Move now has a worker in Zadara read the Azure snapshot directly, which brought a 30 GiB VM to about 20 minutes.

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.