Azure Managed Disks are durable block storage volumes designed for Azure Virtual Machines, offering various performance tiers from Standard HDD to Ultra Disk. Organizations migrating away from Azure often need to transfer data from these disks to alternative providers. Vultr Block Storage provides high-performance SSD and NVMe storage options with straightforward pricing, making it an attractive destination for workloads requiring persistent storage.

This guide explains how to migrate data from an Azure Managed Disk to Vultr Block Storage using Rsync over SSH, including verification steps to ensure data integrity.

Prerequisites

Before you begin, you need to:

• Have a Linux-based Azure Virtual Machine with an attached Managed Disk containing the data to migrate.
• Deploy an Ubuntu 24.04 Vultr Cloud Compute instance and access it as a non-root user with sudo privileges.
• Attach a Vultr Block Storage volume to the Vultr instance with capacity equal to or greater than your source disk.

Set Up the Migration Environment

Prepare both the source Azure VM and destination Vultr instance for the data transfer. This involves mounting the disks and ensuring both are ready to send and receive data.

Set Up the Source Azure Managed Disk

Identify and mount your Azure Managed Disk that contains the data to migrate. Azure VMs typically have a temporary disk that should not be confused with your data disk.

1. Connect to your Azure VM via SSH. Replace USERNAME and AZURE-VM-IP with your credentials.

   console Copy

   $ ssh USERNAME@AZURE-VM-IP
   

   Explain Code

2. List attached block devices to identify your data disk.

   console Copy

   $ lsblk
   

   Explain Code

   Output:

   NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
   sda       8:0    0    30G  0 disk
   ├─sda1    8:1    0  29.9G  0 part /
   ├─sda14   8:14   0     4M  0 part
   └─sda15   8:15   0   106M  0 part /boot/efi
   sdb       8:16   0     8G  0 disk
   └─sdb1    8:17   0     8G  0 part /mnt
   sdc       8:32   0    64G  0 disk /mnt/data_volume

   • sda is the OS disk
   • sdb is the Azure temporary disk (mounted at /mnt by default. Do not use this for persistent data)
   • sdc is the attached Managed Disk containing your data to migrate
   Note

   Azure temporary disks (/dev/sdb) are ephemeral and lose data on VM deallocation. Always verify you're working with the correct data disk.

3. If your data disk is not already mounted, create a mount point and mount it.

   console Copy

   $ sudo mkdir -p /mnt/azure-data
   $ sudo mount /dev/sdc /mnt/azure-data
   

   Explain Code

4. Verify the filesystem and mount.

   console Copy

   $ lsblk -f | grep sdc
   

   Explain Code

   Output:

   sdc     ext4   1.0                   a1b2c3d4-e5f6-7890-abcd-ef1234567890   59.2G     0% /mnt/azure-data

   Note the filesystem type (ext4) to use when formatting the destination volume.

5. Check disk usage.

   console Copy

   $ df -h /mnt/azure-data
   

   Explain Code

   Output:

   Filesystem      Size  Used Avail Use% Mounted on
   /dev/sdc         63G  2.1G   58G   4% /mnt/azure-data

   Note

   If your Managed Disk has multiple partitions, verify each partition's size and filesystem type. You'll need to repeat the mount and transfer steps for each partition, ensuring the destination Vultr Block Storage volume has sufficient capacity.

Set Up the Destination Vultr Block Storage Volume

Format and mount the destination Vultr Block Storage volume to receive the migrated data.

1. Connect to your Vultr instance via SSH. Replace VULTR-IP with your credentials.

   console Copy

   $ ssh linuxuser@VULTR-IP
   

   Explain Code

2. List attached block devices.

   console Copy

   $ lsblk
   

   Explain Code

   Output:

   NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
   vda    253:0    0   55G  0 disk
   ├─vda1 253:1    0  512M  0 part /boot/efi
   └─vda2 253:2    0 54.5G  0 part /
   vdb    253:16   0   80G  0 disk

   vdb is the attached Vultr Block Storage volume. Additional volumes appear as vdc, vdd, etc.

3. Create a GPT partition table on the volume.

   console Copy

   $ sudo parted -s /dev/vdb mklabel gpt
   

   Explain Code

4. Create a primary partition that uses the entire disk.

   console Copy

   $ sudo parted -s /dev/vdb unit mib mkpart primary 0% 100%
   

   Explain Code

5. Format the partition with the same filesystem as the source disk.

   console Copy

   $ sudo mkfs.ext4 /dev/vdb1
   

   Explain Code

6. Create a mount point and mount the partition.

   console Copy

   $ sudo mkdir -p /mnt/vultr-storage
   $ sudo mount /dev/vdb1 /mnt/vultr-storage
   

   Explain Code

7. Set ownership so your user can write to the volume.

   console Copy

   $ sudo chown -R $USER:$USER /mnt/vultr-storage
   

   Explain Code

8. Verify the mount.

   console Copy

   $ df -h /mnt/vultr-storage
   

   Explain Code

   Output:

   Filesystem      Size  Used Avail Use% Mounted on
   /dev/vdb1        79G   24K   75G   1% /mnt/vultr-storage

9. (Optional) Add the volume to /etc/fstab for persistent mounting across reboots.

   console Copy

   $ echo "UUID=$(sudo blkid -s UUID -o value /dev/vdb1) /mnt/vultr-storage ext4 defaults 0 2" | sudo tee -a /etc/fstab
   

   Explain Code
   Note

   If your source Azure Managed Disk has multiple partitions, configure matching partitions on the Vultr Block Storage volume with the same filesystem format and equal or greater capacity.

Migrate Azure Managed Disk Data to Vultr Block Storage

Use Rsync to copy files from the Azure Managed Disk to the Vultr Block Storage volume. Rsync transfers data over SSH, compresses during transit, and can resume interrupted transfers.

1. Verify Rsync is installed on both instances.

   console Copy

   $ rsync --version
   

   Explain Code

   If not installed on either system:

   console Copy

   $ sudo apt install rsync -y
   

   Explain Code

2. From the Azure VM, start the transfer. Replace VULTR-IP with your Vultr instance credentials.

   console Copy

   $ sudo rsync -avz --progress --exclude="lost+found" /mnt/azure-data/ linuxuser@VULTR-IP:/mnt/vultr-storage/
   

   Explain Code
   • -a: Archive mode (preserves permissions, timestamps, symbolic links)
   • -v: Verbose output
   • -z: Compress data during transfer
   • --progress: Show transfer progress
   • --exclude="lost+found": Skip the system recovery directory

   Output:

   sending incremental file list
   ./
   app-data/
   app-data/config.json
             1,234 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=42/44)
   ...
   sent 2,147,483,648 bytes  received 1,024 bytes  15,432,098.76 bytes/sec
   total size is 2,147,483,648  speedup is 1.00

   Note

   Transfer time depends on data size and network speed. For large volumes, consider running the command in a screen or tmux session to prevent interruption if your SSH connection drops.

3. If the transfer is interrupted, re-run the same command. Rsync automatically resumes by transferring only the remaining files.

Test the Vultr Block Storage Volume

After migrating the data, verify integrity by comparing checksums between the source and destination volumes to ensure no files were corrupted during transfer.

1. On the Azure VM, generate checksums for all files.

   console Copy

   $ find /mnt/azure-data -type f ! -path "*/lost+found/*" -exec sha256sum {} \; | sort > ~/azure_checksums.txt
   

   Explain Code

2. Transfer the checksum file to the Vultr instance.

   console Copy

   $ scp ~/azure_checksums.txt linuxuser@VULTR-IP:~/
   

   Explain Code

3. On the Vultr instance, generate checksums for the migrated files.

   console Copy

   $ find /mnt/vultr-storage -type f ! -path "*/lost+found/*" -exec sha256sum {} \; | sort > ~/vultr_checksums.txt
   

   Explain Code

4. Normalize paths in the Azure checksum file to match Vultr paths.

   console Copy

   $ sed 's|/mnt/azure-data|/mnt/vultr-storage|g' ~/azure_checksums.txt > ~/azure_checksums_normalized.txt
   

   Explain Code

5. Compare the checksum files.

   console Copy

   $ diff ~/azure_checksums_normalized.txt ~/vultr_checksums.txt
   

   Explain Code

   No output indicates all files match. If differences appear, re-run Rsync to transfer any missing or corrupted files.

6. Verify directory sizes match.

   • On Azure VM:

     console Copy

     $ du -sh /mnt/azure-data
     

     Explain Code

   • On Vultr instance:

     console Copy

     $ du -sh /mnt/vultr-storage
     

     Explain Code

   The sizes should be nearly identical (minor differences may occur due to filesystem overhead).

Cutover to Vultr Block Storage

After you verify data integrity, complete the transition by performing a final sync and updating your application configurations.

1. Final sync: Capture any changes made since the initial transfer.

   console Copy

   $ sudo rsync -avz --progress --exclude="lost+found" /mnt/azure-data/ linuxuser@VULTR-IP:/mnt/vultr-storage/
   

   Explain Code

2. Update application configurations to reference the new storage path on the Vultr instance.

3. Update DNS records to point to the Vultr instance's public IP address if your applications are publicly accessible.

4. Test thoroughly to ensure applications function correctly with the migrated data.

Conclusion

You have successfully migrated data from an Azure Managed Disk to Vultr Block Storage using Rsync. This guide walked through preparing both storage volumes, transferring data securely over SSH, and validating integrity with checksum comparison. Your data now resides on Vultr's high-performance block storage infrastructure. For more information on managing Vultr Block Storage, including resizing and snapshots, visit the Vultr Block Storage documentation.