Migrating Linode Block Storage to AnubizHost Storage VPS

List Block Storage volumes from the Cloud Manager. Note size, filesystem type (ext4, xfs), mount point on the source Linode, and current usage. For each volume, plan an equivalent disk allocation on the AnubizHost storage VPS.

For volumes mounted as data disks (not boot), the migration is just rsync of the contents. Boot disks are migrated as part of the full VPS migration described in our other Linode guide.

Order a storage VPS with enough disk to hold all your Linode volumes plus 20% headroom. Romania storage VPS is cheapest; Iceland and Netherlands offer more bandwidth. Create matching mount points (/mnt/data1, /mnt/data2, etc.) and format with the same filesystem type the source uses.

For high-throughput workloads, consider AnubizHost dedicated storage servers with NVMe arrays for IOPS-sensitive applications like databases or video editing.

For each Linode Block Storage volume, rsync from source to destination:

rsync -avHAX --numeric-ids --delete \
  /mnt/source-volume/ \
  root@NEW_IP:/mnt/dest-volume/

For very large volumes, run an initial sync hours before cutover, then a final delta sync immediately before the mount swap. This keeps the cutover window short.

Unmount the Linode volumes on the source. Mount the new AnubizHost paths on the target server (or remote-mount via NFS/SSHFS from the storage VPS). Update application config that references mount paths.

For databases and other write-intensive workloads, schedule a brief downtime window for the final sync and mount swap. Most operations tolerate 5-15 minutes of unavailability for a clean migration.

AnubizHost storage VPS is unmetered within plan limits. For NFS or iSCSI exposure to multiple application servers, install nfs-kernel-server or tgt on the storage VPS. Snapshot strategy: nightly rsync to a second AnubizHost VPS or rclone to offshore object storage. Related reading: offshore storage, encrypted backups, Linode migration.