Applicable to:
- SolusVM
Question
How to move/migrate the SolusVM Master to the new server?
Answer
-
Deploy the new dedicated server and install Master SolusVM on it.
-
Back up the database of the source Master SolusVM, browse to Dashboard > Tools > Database, and click on Download.
Note: there will be a .gz file, use any tool to extract its content.
-
Parts of SolusVM Master database are encoded using a unique encryption key stored in
/usr/local/solusvm/includes/solusvm.conf
. The format of thesolusvm.conf
is as follows:CONFIG_TEXT: <DATABASENAME>:<USER>:<PASSWORD>:<HOST>:<the key is the last entry>
Replace the <the key is the last entry> part in the
solusvm.conf
on the new server with <the key is the last entry> part from thesolusvm.conf
from the old serverSVM_WARN: If this step is missing, none of your passwords or slave connections will work.
-
After that, upload the mysql dump of the SolusVM database to the new server and restore it on the new server:
Note: the extracted file with the mysql dump has no extension - this is expected, proceed with this file.
# /usr/bin/mysql --user=USER --password=PASSWORD DATABASENAME < database
USER, PASSWORD, DATABASE should be taken from the new
solusvm.conf
file. -
Move templates from the old server to the new one. The location of templates is below:
/home/solusvm/kvm/templates
- for KVM templates/home/solusvm/xen/templates
- for Xen templates/vz/template/cache
- for OpenVZ templates -
Copy the SSL certificate from the old master node to the new one, certs are at the locations:
/usr/local/svmstack/nginx/ssl/ssl.crt
/usr/local/svmstack/nginx/ssl/ssl.key
/usr/local/solusvm/includes/nvnc/cert.pemNote: In case you are migrating from the old SolusVM version with lighttpd web server running, the SSL certificate location on the old server would be
/usr/local/solusvm/ssl/
.
- In the client area reissue the license to reset the IP address binding.
- In SolusVM > Nodes > List nodes > Edit localhost node, replace the IP address with the new IP address of the master node.
- Remove the
/usr/local/solusvm/data/allow.dat
and/usr/local/solusvm/data/ftp.dat
files on every slave server right after the old master node is stopped. - In case the master server is integrated with WHMCS, change the IP address of the master node at WHMCS Product/Services Servers.
Comments
0 commentsPlease sign in to leave a comment.