Search Engine: Elastic

Article ID: 112276, created on Sep 14, 2011, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation


This article describes the upgrade procedure for Parallels Virtuozzo Containers (PVC) 3.x for Linux/Windows registered to the Parallels Virtuozzo Containers version 4.x in POA .
Note: PVC for Linux does not support a direct upgrade from version 3.x to 4.7. Refer to article #112388 for details. 

The "Migration to PVC 4.x" feature was made available with POA 5.2 update 4.
 #111809 POA 5.2 Update 4 (KB111809)
For a description of the feature, refer to "Upgrading 3.x VPS Hosting Hardware Node to 4.6 Version" in the VPS Hosting Deployment Guide

Review the feature limitation at the following article:
#112259 Limitations of the "Migration to PVC 4.x" feature in POA 5.2

To upgrade a PVC registered to the 4.x version, perform the following actions:

0. Check set consistency
You should check that all VPSes on VZ hw node are valid, i e :
- VPSes are created based on existing subscription
- refer to valid RT
This condition are violated only for broken MN DB, and VZ upgrade will fail on it
To check conditions, perform SQL quiry on MN DB:
> select host_id, owner_id, subscription_id, primary_name, hw_host_id from hosts where subscription_id not in (select sub_id from subscriptions) order by host_id;
Query should return 0 records. If no, delete the returned hosts, and delete VPSes with these ids:
Top> Service Director> Virtuozzo Manager> VPS Hardware Nodes > [VZ node] > VPSes, select vps to delete, press "Delete"

To check the RT, enter the RT screen of hosted VPSes RT.
> Service Director> Provisioning Manager > Resource Types> [RT] > Activation Parameters
There should be no error on screen, like "Inconsistent Resource Type". Else, you need to recover RT, please consult POA maintenance

1. Disable Service Templates

Before a PVC upgrade, all service templates that use PVC 3.x for service provisioning should be disabled to avoid service provisioning on nodes that are not synchronized .
In POA, go to Top -> Service Director -> Provisioning Manager -> Service Templates -> deactivate all service templates that use PVC 3.x nodes for service provisioning.

If POA is integrated with PBA-E, corresponding service plans also will be automatically disabled.

2. Upgrade All PVC 3.x Nodes to Version 4.x

Follow the PVC upgrade recommendation provided in the following correspondence guides:

        Parallels Virtuozzo for Windows:
        Refer to the PVC for Windows Upgrade Guide for upgrade details.
        See the chapter Upgrading from SWsoft Virtuozzo 3.5.1 Service Pack 1.

        Parallels Virtuozzo for Linux:
        Since PVCfL does not support a direct upgrade from version 3.x to 4.7, choose one of the following migration paths:

2.1. Using two PVC nodes:
a. Register a brand new PVCfL 4.7 server in POA. Make sure that the PVA agent 4.6.3-1777 is installed. Refer to article #9445.
b. Upgrade PVCfL 3.x node to PVCfL 4.0 following steps 1 and 2 from article #112334.
c. Synchronize the upgraded node in POA as described in 4. "Synchronization" step.
d. Using the POA interface, migrate all containers from the upgraded server to the PVCfL 4.7 node registered on step a.
e. Remove the upgraded server from POA 
2.2. Using one PVC node:
a. Upgrade PVCfL 3.x node to PVCfL 4.7. Refer to article #112334.
b. Synchronize the upgraded node in POA as described in 4. "Synchronization" step.


2.3. On PVCfL 4.6 version:
a. Upgrade the PVCfL 3.x node to PVCfL 4.6. Refer to the chapter "Upgrading from SWsoft Virtuozzo 3.0 Service Pack 1" from the PVC for Linux Upgrade Guide
b. Synchronize the upgraded node in POA as described in 4. "Synchronization" step.

3. Check PVA agent is working

Make sure that PVA agent on VZ hw is working and listening the proper tcp port. Execute from MN:
# telnet <VZ hw ip> 4433
connection should be established.

On VzLin, PVA agent sometimes fail to update. Check agent availability:
# /etc/init.d/pvaagentd status
If there is no agent, see vz update log for details: /root/vzinstall.log
Most frequent reason is absence of from cups-libs rmp (it should be written in vzinstall.log). In that case you should install cups-libs from yum. If your Vz hw is CentOS 4, setup yum to use legacy repository:
Run agent setup
/var/lib/pva_setup/pva-setup start

4. Synchronization

After the upgrade, all nodes should be synchronized in POA.

In POA, go to TOP -> Service Director -> Virtuozzo Manager -> VPS Hardware Nodes ->  Click on the upgraded Hardware Node ->
Click the Synchronize after upgrade to version 4.x link.

For the synchronization, it is necessary to specify the following parameters:
  • Hardware node address - IP address of the Hardware node
  • Username -. Hardware Node root/Administrator user name
  • Password - Hardware Node root/Administrator password
There are different registration methods for the PVC 3.x and 4.x nodes. The PVC 3.x node is registered by the IP address of the service container, but PVC 4.x is registered by the IP address of the hardware node.

Complete the synchronization wizard by clicking the Submit button.

This step should be repeated for all upgraded PVC nodes.

Note: After a successful PVC upgrade, the existing VPS resource types will be cloned. The Cloned Resource Type has a [VZ3 to VZ4 Upgrade] prefix in its name and corresponds to the 4.6 version of PVC. After all PVC nodes are upgraded to version 4.x, all VPSes Resources Types will be switched automatically to the cloned Resource Types. Old resource types will be deleted.

4. Activate Service Templates

Activate disabled service templates when synchronization for all nodes is completed.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF