User`s guide

Upgrading from SWsoft Virtuozzo 3.0 Service Pack 1 13
 The "Virtuozzo Control Center Users Self-Registration" functionality present in previous
versions of the Virtuozzo software and used by new users to self-register in Virtuozzo
Control Center and request Containers is no longer supported in Parallels Virtuozzo
Containers 4.6. Instead, you can register external user databases in Parallels Virtual
Automation and allow any users from the registered databases to request Containers by
assigning the Workflow User role to these users.
 The submitted VE requests are not kept in Parallels Virtual Automation after upgrading to
Parallels Virtuozzo Containers 4.6. Processed the necessary requests before the upgrade.
 The disabled Virtuozzo Control Center users are not kept after upgrading to Parallels
Virtuozzo Containers 4.6. To preserve a VZCC user, make sure that her or his login is
enabled before starting the upgrade procedure.
 The settings related to the Container requesting functionality are not kept after
upgrading to Parallels Virtuozzo Containers 4.6. To re-enable this functionality, follow the
Workflow link under the Management group on the Parallels Virtual Automation left menu
and configure the necessary settings on the Setup tab of the Workflow window.
 After upgrading Hardware Nodes running the Virtuozzo 3.0 software and participating in a
Virtuozzo cluster to Parallels Virtuozzo Containers 4.6, their membership in the cluster is
not kept. To continue centrally managing your Nodes using Parallels Virtual Automation,
create a new group and include all the upgraded Hardware Nodes in this group.
 Logging in to a Hardware Node via Parallels Virtual Automation and Parallels Management
Console with the vzagent credentials is not supported after upgrading the Node to
Parallels Virtuozzo Containers 4.6. Use the root credentials instead.
 After upgrading to Parallels Virtuozzo Containers 4.6, execute the following command on
the Hardware Node (or on the Master Node if you have united your Nodes into a group) to
update all Container backup caches:
# /opt/vzagent/bin/vzbackupsync
This is needed for the vzbackup and vzabackup utilities and the Parallels tools to
correctly display the existing Container backups on the Hardware Node. Run the same
command on a Hardware Node if the backups of Containers residing on this Node were
stored on a remote storage before the upgrade.
 Hardware Nodes running Virtuozzo 3.0 Service Pack 1 and upgraded to Parallels Virtuozzo
Containers 4.6 continue using VZFS v1. That means that all legacy Containers on the
upgraded Nodes continue operating on VZFS v1 and all new Containers are also created on
the basis of this VZFS version. If you want to use VZFS v2 (which is the default VZFS
version on Hardware Nodes with fresh installations of Parallels Virtuozzo Containers 4.6)
on the upgraded Nodes, do the following:
a Ascertain that the value of the VEFORMAT parameter in the global configuration file
(/etc/vz/vz.conf) is set to vz4.
b Recreate the caches of all EZ OS templates installed on the Node by running the
following commands:
# vzpkg remove cache EZ_OS_Template_Name
# vzpkg create cache EZ_OS_Template_Name
 All legacy Containers on the upgraded Hardware Nodes will continue using the old
Container directory layout. To convert these Containers to use the new Container layout,
execute the following command:
# vzctl convert CT_ID
You need to upgrade a Container to use the new directory layout if you plan to store the
Container private area on a shared storage (as it is the case in failover and data sharing
clusters). In all other cases, the upgrade to the new layout is not required.