Migrating Linode (Akamai) to AnubizHost

From the Cloud Manager, capture instance plan (Shared, Dedicated, High Memory, etc.), region, attached Block Storage volumes, Reserved IP, and any Cloud Firewall rules. Linode Shared 4GB maps to AnubizHost VPS III.

If you use Linode DNS Manager, export zones via the API. Lower TTLs 24 hours ahead on any record pointing at the Linode IP.

Order an offshore VPS matching the Linode plan. Pay with BTC or XMR. SSH in, install package list from the source. Replicate Cloud Firewall rules as ufw/nftables: each Cloud Firewall stanza becomes a ufw allow line.

For Linode Object Storage migrations, use rclone with the s3 backend pointing at the Linode endpoint as source, MinIO on AnubizHost as destination - same flow as our DigitalOcean Spaces guide.

Standard rsync from running Linode:

rsync -aHAXv --numeric-ids --delete \
  --exclude={"/dev","/proc","/sys","/tmp","/run","/mnt","/media","/lost+found"} \
  / root@NEW_IP:/

For Block Storage volumes attached to the Linode, mount on the source and rsync each separately to corresponding mount points on the target.

Flip A/AAAA records. Re-issue Let's Encrypt on the new host. Keep Linode active for 7 days as rollback. Verify with external curl and your monitoring stack before decommissioning.

Linode/Akamai bills monthly with no proration on cancellation. Time cutover to mid-billing cycle to avoid double-paying for a partial cycle.

Akamai is a US enterprise vendor with enterprise-style abuse response. AnubizHost is small-vendor, offshore, and crypto-billed. For privacy-sensitive workloads, the jurisdiction shift is the main benefit. Related reading: offshore VPS, Linode Block Storage migration, anonymous hosting.