Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Migrate Solusvm VPS from OpenVZ 6 to OpenVZ 7 – How to do

by | Jul 3, 2021

Wondering how to migrate Solusvm VPS from OpenVZ 6 to OpenVZ 7? We can help you!

We often get requests from our customers to migrate VPSes from the old SolusVM master with OpenVZ 6 to a new SolusVM master with OpenVZ 7.

Here at Bobcares, we often handle these requests as a part of our Server Management Services. Today we will see how our Support Engineers do this for our customers.

How to Migrate Solusvm VPS from OpenVZ 6 to OpenVZ 7

Now we will see the steps that our Support Engineers follow to do this migration.

Here we will migrate containers from a server running Virtuozzo Containers for Linux 4.7 or OpenVZ with kernels 2.6.18 and 2.6.32 to a Virtuozzo Hybrid Server 7 server.

We must ensure that the source node can connect to the destination node via SSH.

Steps to follow are given below:

1. Firstly we have to Install an SSH key on the destination server for the root user.

2. To do this, we can use the following command and generate a key on the source server:

# ssh-keygen -t rsa

3. After that we can use the following command to transfer the key to the destination server:

# ssh-copy-id [email protected]<dest_server>

4. Now we will clone the script repository to the source OpenVZ server  using the following command:

# git clone https://src.openvz.org/scm/ovzl/ovztransfer.git

5.  Then we will change the permission of the directory using the following command:

# chmod 755 ovztransfer.sh

6. Next we will stop the containers that we wish to migrate.

7. We can Initiate migration on the source OpenVZ server with the following command:

# ./ovztransfer.sh <dest_server> <source_CT1_ID>[:<new_CT1_name>] \
[ ... <source_CTn_ID>[:<new_CTn_name>]]

8. Then we can tweak script behavior with the following environment variables:

  • OVZTR_METHOD, can be tar+ssh (default) or rsync. With the default tar+ssh, the container data is packed using tar, passed via pipe and SSH to the destination node, and unpacked.
  • And with rsync, the container data is copied to the destination using rsync over SSH.
  • OVZTR_COMPRESS, can be 0 (disabled) or 1 (enabled). If we enable toggles compression during data transfer it adds the -z option to tar or rsync.

Note: However, we must keep in mind that enabling compression saves network traffic but results in higher CPU load.

9. After migration completes it is necessary to re-register them in SolusVM and assign to the new node.

Following are the steps to do this:

a) Firstly we need to connect to the Master node over SSH.

b) Then we need to update the master node database with the new location of VPS with the following command:

# /scripts/vm-migrate ID NEWNODEID

Here, “ID” of the migrated VPS, can be seen from the column ID in SolusVM > Virtual Servers.

And  “NEWNODEID”  is the ID of the target node, which can be seen in SolusVM > Nodes.

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to migrate Solusvm VPS from OpenVZ 6 to OpenVZ 7 for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF