Upgrading Virtuozzo 6 with Local Storage
This section describes how to upgrade your Virtuozzo 6 servers with local storage to Virtuozzo Server 7. You can do this by using spare servers or in-place or migrate VMs and containers to new servers running Virtuozzo Server 7. Apply either method to each server in your Virtuozzo 6 infrastructure.
Upgrading with Spare Virtuozzo 6 Servers
To upgrade by using a spare Virtuozzo 6 server, do the following:
Update both the Virtuozzo 6 server to be upgraded and the spare server to the latest version. You can do this by running
yum updateon each server.The oldest Virtuozzo 6 build eligible for upgrade is 6.0.11-3466.Back up all VMs and containers on the Virtuozzo 6 server to be upgraded. You can do this with the
pbackuptool as described in the Virtuozzo 6 User’s Guide and use both Virtuozzo 6 and 7 hosts as backup servers.Temporarily migrate VMs and containers from the Virtuozzo 6 server to be upgraded to the spare Virtuozzo 6 server. You can do this with the
pmigratetool as described in the Virtuozzo 6 User’s Guide.Perform a fresh install of Virtuozzo Server 7 on the Virtuozzo 6 server to be upgraded. For instructions, see the Installation Guide.
Migrate VMs and containers back to the upgraded server from the spare server. For more details, see Migrating VMs and Containers from Virtuozzo 6 to Virtuozzo Server 7.
If you store VM and container backups on a Virtuozzo 6 server, move them to Virtuozzo Server as described in Restoring Virtuozzo 6 Backups to Virtuozzo Server 7.
Upgrading by Migrating to New Servers
To upgrade by migrating to a new server running Virtuozzo Server 7, do the following:
Update the selected Virtuozzo 6 server (from which you will migrate VMs and containers) to the latest version. You can do this by running
yum update.The oldest Virtuozzo 6 build eligible for upgrade is 6.0.11-3466.Back up all VMs and containers on the selected Virtuozzo 6 server. You can do this with the
pbackuptool and use both Virtuozzo 6 and 7 hosts as backup servers.Perform a fresh install of Virtuozzo Server 7 on a different (new) server. For instructions, see the Installation Guide.
Migrate VMs and containers to it from the selected Virtuozzo 6 server. For more details, see Migrating VMs and Containers from Virtuozzo 6 to Virtuozzo Server 7.
If you store VM and container backups on a Virtuozzo 6 server, move them to a server running Virtuozzo Server 7 as described in Restoring Virtuozzo 6 Backups to Virtuozzo Server 7.
Upgrading In-Place with Local Storage
Hardware nodes that host only containers and no virtual machines can be upgraded to Virtuozzo Server 7 in-place. To be eligible for in-place upgrade, the hardware node must meet the following requirements:
Updated to the latest version of Virtuozzo 6.
The oldest Virtuozzo 6 build eligible for upgrade is 6.0.11-3466.No virtual machines.
No containers that use VZFS.
No templates for guest operating systems unsupported by Virtuozzo Server 7.
For the upgrade, you will need the following:
- Contents of the Virtuozzo Server 7 distribution, either on a disc mounted to a local directory or available over network via HTTP.
- A Virtuozzo Server 7 license (optional). The existing Virtuozzo 6 license is not transferred during the upgrade. You can install a new Virtuozzo Server 7 license during the upgrade or skip this step and install one manually after the upgrade with the
vzlicloadtool.
Note the following:
- If any containers on the Virtuozzo 6 node are set to be started automatically on reboot, they will do the same once you boot to Virtuozzo Server 7 after the upgrade.
- In the end of the upgrade,
yum updateis launched by default to update to the latest Virtuozzo Server 7 version from the configured repositories. You can skip this step if required. - Upgrade logs can be found in the
/var/log/vzupgrade.logand/var/log/redhat*logfiles.
To perform an in-place upgrade of a Virtuozzo 6 node to Virtuozzo Server 7, do the following:
Install the vzupgrade package:
1# yum install vzupgradeCheck for conditions blocking the upgrade (listed earlier):
1# vzupgrade check --blockerThe list of upgrade blockers is also displayed byvzupgrade list.If no blockers exist, run the
vzupgrade installcommand. For example:1# vzupgrade install --boot /dev/sda --license <license_key> --rebootFor details on each option, see Upgrade Tool Reference.The installer will run a pre-upgrade check and generate upgrade scripts (if required, you can perform this step manually before upgrading with
vzupgrade check).Having collected the required information, the installer will display a list of things to be aware of. Read the list, and, if you agree to proceed, press Y and Enter.
If
--rebootis omitted, reboot the hardware node when asked by the installer. Make sure to boot from the hard drive and choose the system upgrade option in the upgrade bootloader. From this moment, the actual upgrade will start and no further interaction on your part will be required.
/var/lib/upgrade_pkgs.When the upgrade completes, the node will automatically reboot to Virtuozzo Server.
Upgrade Tool Reference
| |
| Option | Description | |
|---|---|---|
--device <mount_point> | Mutually excludes --network. The mount point of the device with Virtuozzo Server distribution contents (e.g., a USB flash drive). | |
--network <distrib_URL> | Mutually excludes --device. The path to the Virtuozzo Server installation ISO image or its contents (full or netinstall). | |
--license <key> | Specifies the Virtuozzo Server license key. | |
--skip-license-upgrade | Skips license installation during upgrade. You can install a Virtuozzo Server license after the upgrade with the vzlicload tool. | |
--add-repo <name>=<repository_URL> | Specifies remote Virtuozzo Server and VzLinux repositories (space-separated). | |
--boot <bootloader_destination> | Specifies destination to install Virtuozzo Server bootloader to. If omitted, the Virtuozzo Server bootloader will not be installed and the existing Virtuozzo 6 bootloader will be modified to boot Virtuozzo Server. Third-party bootloaders need to be updated manually if the Virtuozzo Server bootloader is not installed. | |
--reboot | Automatically reboots the node to the upgrade bootloader. | |
--skip-post-update | Skips the launch of yum update in the end of the upgrade. | |
--clean-cache | Cleans up packages from /var/lib/upgrade_pkgs on start so they are downloaded anew during installation. If this option is omitted (default), packages already stored in /var/lib/upgrade_pkgs are checked against those in the repository, updated if necessary, and used. | |
-h,--help | Shows usage information. | |
If the options --device, --network, and --add-repo, are omitted, the default repositories are used:
| |