Seeking Advice on Migrating VPS from a reseller platform that uses OnApp to Virtualizor

M

Minhaz

New member
Hi everyone,

I hope you're all having a great weekend!

I recently set up my own VPS hypervisor using Virtualizor and am looking for advice on how to efficiently migrate my current client’s VPS to my new Virtualizor setup. I am currently using a VPS reseller platform that is based on OnApp.

The challenge is that I do not have direct access to the hypervisor where my client’s VPS are hosted—I only have root access to the VPS themselves.

Does anyone have any tips or strategies for migrating the VPS, ideally with minimal downtime and effort? Any insights would be greatly appreciated!

Thank you all in advance!
 
Hello,

I hope this will help you

  1. Using rsync for Live Migration:
    • One of the most efficient ways to transfer data is through rsync. This allows you to synchronize data between the source VPS and your new Virtualizor server incrementally, minimizing downtime.
    • Start by running an initial rsync pass while the client’s VPS is still active:

      rsync -avz --exclude=/proc --exclude=/sys --exclude=/dev --exclude=/tmp --exclude=/run user@source_vps:/ /destination_mount_point/<br>


    • Once ready for the final migration, stop the services on the original VPS, perform a final rsync to capture any last-minute changes, and then switch DNS/traffic to the new server.
  2. Creating Disk Images:
    • If feasible, create a compressed disk image of the VPS using tools like dd:



      <span>dd</span> <span>if</span>=/dev/sda | gzip &gt; /path/to/vps-image.gz<br>
    • Transfer the image to your new hypervisor and restore it:


      gunzip -c /path/to/vps-image.gz | <span>dd</span> of=/dev/sdb<br>
    • Note: Ensure that the storage configuration on the new Virtualizor matches the original disk structure for compatibility.
  3. Custom Backup and Restore:
    • Leverage backup tools (e.g., tar or rsnapshot) to create comprehensive backups of the VPS data and configurations. Transfer these backups to the new server, extract them, and reconfigure services if needed.
  4. Manual Service Migration:
    • For minimal disruption, consider migrating services (like web servers, databases, etc.) individually by setting up the same services on the new VPS and replicating data.
    • Use tools like mysqldump for databases and scp/rsync for web files.
  5. Network Configurations:
    • Plan DNS updates ahead of time to ensure a smooth switch with minimal downtime. Lower the TTL (Time to Live) on DNS records well before migration to allow for quicker propagation during the switchover.
  6. Testing Phase:
    • Before finalizing, test the new VPS setup thoroughly to ensure all applications and services run as expected.
If you need more specific assistance or run into any issues during the migration, feel free to ask!

Best of luck with your migration
 
You must log in or register to reply here.

Supporters

Back
Top