Move SolusVM Master

It’s possible to deploy a SolusVM master then host VPS servers on your master. This saves having to also deploy a slave which would add further costs. If you deploy SolusVM master to a dedicated server then you can setup VPS servers on the master. You cannot host VPS servers on a SolusVM master that is running on a VPS Server. You can move the SolusVM Master.

So what if you created a SolusVM master and deployed VPS Servers to the master then you decide to move your master to a VPS server. Here we will show you how to create a new SolusVM Master and Move SolusVM Master to the new VPS we will also convert the old master into a slave.

Create a new SolusVM Master

First, partition your server according to the SolusVM documentation at https://documentation.solusvm.com/display/DOCS/SolusVM+Installer++-+Version+4

Next, create a new Master on your VPS, run the installer.

wget https://files.soluslabs.com/install.sh
sh install.sh

Download Your Database

Now you should have two masters. On your old master login to the SolusVM admin control panel and download your database. You can download it directly to your desktop or send it to your email.

Your database details are located at /usr/local/solusvm/includes/solusvm.conf

The format is: [DATABASENAME]:[USER]:[PASSWORD]:[HOST]:[ENCRYPTIONKEY]

You can use these details to take a copy of the database using SSH and MYSQL

Using SSH and MYSQL to Generate A Database Backup

mysqldump -p -u username database_name > dbname.sql

Upload your SolusVM Database

Using the SQL you just got from your old master upload it to your new master and import it into your new master’s database. Your database details for the new master will be located at /usr/local/solusvm/includes/solusvm.conf

Use the command to import the SQL switching the USER, PASSWORD and DATABASENAME for the details in the solusvm.conf file

/usr/bin/mysql --user=USER --password=PASSWORD DATABASENAME < database.sql

Restore your Slave Connections

Remove the file /usr/local/solusvm/data/allow.dat on each slave which will then allow your slaves to connect to your new master, If your slaves cannot connect just add your new masters IP to the /usr/local/solusvm/data/allow.dat file on each slave

Upload Your Templates

If your new Master is a VPS it’s likely you won’t have a /vz/cache/templates file to place your templates in. So just create the folder and RSYNC or upload your templates to this folder.

Next, on your old master run the SolusVM installer again. Don’t worry, this won’t touch any of your VPS servers, we are just converting it from a Master to a Slave

wget https://files.soluslabs.com/install.sh
sh install.sh

Ignore the Warning that SolusVM is already installed and choose option 6 to set up a new Slave. Once complete you will have a new ID Key Use this to add a new Slave to your Master. Remember to change your New Masters IP address in the node configuration under “localhost” this will still be displaying your old masters IP.

Finally, we need to tell the master where the old VPS servers are located. So, you can use the /scripts/vm-migrate script to do this. On your master in SSH issue the command

/scripts/vm-migrate [VSERVERID] [NEWNODEID]

Switch [VSERVERID] for one of the VPS servers VSERVERIDs that was on your old master but is now on the slave. Switch [NEWNODEID] for the ID of the Slave you just created. You can get this from NODES > LIST NODES. It’s the number on the left.

<VSERVERID> is the ID listed in your VM list in SolusVM
<NEWNODEID> is the ID of the node listed in your Node List in SolusVM.

You should receive a confirmation message that the master has updated the location for that VPS and, in your master it should now show as online and not offline. Repeat this process for all the VPS servers on your new Slave.

Remember to generate a new SSL Certificate for your SolusVM Master to prevent in-browser warnings.

How was this article? Move SolusVM Master

Click to rate this post!

[Total: 23 Average: 5]

Spread the love