Importing Virtual Machines from SolusVM 1 to SolusVM 2 Utilizing Cluster Import

Have more questions? Submit a request

Applicable to:

  • SolusVM

Question

Importing Virtual Machines from SolusVM 1 to SolusVM 2 Utilizing Cluster Import

Answer

Import is a one-time process that enables SolusVM 2 to recognize and manage slave nodes and hosted VPSes in a SolusVM 1 cluster. It involves creating a new master node (called "management node" in SolusVM 2) and connecting all existing slave nodes (called "compute resources" in SolusVM 2) to it. Here is what the outcome of a successful import should look like:

  • You have a fully operational SolusVM 2 management node connected to and able to manage all existing compute resources and virtual servers.
  • All existing virtual servers and clients (called "customers" in SolusVM 2) are carried over and can be managed in SolusVM 2 (with certain limitations listed below).
    Existing customers can log in to SolusVM 2 and manage their servers.
  • Integration with WHMCS (if any) is preserved. You can sell your services, sign up new customers, and keep billing existing ones.

Once the import is over, we strongly recommend that you stop the SolusVM 1 agent on all imported nodes by running the following command

# /usr/local/solus/bin/agent services-solusvm1 off

and only manage them via the SolusVM 2 management node. If you have imported every slave node in SolusVM 1 and there are no virtual servers hosted on the master node itself, the SolusVM 1 master node can be decommissioned.

 

A comprehensive guide for Cluter Import usage can be found here: https://docs.solusvm.com/v2/administrator-guide/Importing%2BSolusVM%2Bv1%2BClusters.html

 

 

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.