This section provides instructions how to upgrade PVC from version 3.x to version 4.x for Linux/Windows VPS Hardware Node, where the Shared VPSs are created.
To upgrade PVC for Linux/Windows installed on VPS Hardware Nodes, perform the following actions:
1 From the VPS Hardware Node which is planned for upgrade, migrate all VPSs of Dedicated type to some other VPS Hardware Node. For VPS migration instructions,
refer to POA Provider's Guide, VPS Hosting in POA > Managing VPS > Migrating Virtual Private
Servers section.
It is necessary to migrate Dedicated VPSs only; upgrading VPS Hardware Nodes with
Shared VPSs installed is supported by POA.
Important: After the upgrade, the Dedicated VPSs based on PVC 3.x format cannot be
migrated back to the source VPS Hardware Node, as they will become incompatible with the new VPS Hardware Node platform (PVC 4.x). The ability to upgrade VPS Hardware Nodes with Dedicated VPSs installed will be supported since POA 5.0. Currently we can recommend the following workaround: migrate permanently all
Dedicated VPSs from all VPS Hardware Nodes to separate VPS Hardware Node(s),
which will continue working on the PVC 3.x platform. After POA 5.0 is released, you can upgrade these VPS Hardware Node(s) to PVC 4.x.
2 Log on to the VPS Hardware Node via SSH/RDP as root/Administrator user. 3 Upgrade PVC from 3.x to 4.x following the instructions at:
http://download.parallels.com/virtuozzo/virtuozzo4.0/docs/en/win/VzWindowsUpgra de.pdf - for Windows-based VPS Hardware Node
http://download.parallels.com/virtuozzo/virtuozzo4.0/docs/en/lin/VzLinuxUpgrade.pd f - for Linux-based VPS Hardware Node
Note: It is recommended to install all available updates for PVC 4.x after the upgrade is
completed.
4 Re-create the Service Container following the instructions at
http://kb.parallels.com/en/1089 (for Linux-based VPS Hardware Node) and
http://kb.parallels.com/en/3608 (for Windows-based VPS Hardware Node).
5 Depending on your POA Management Node platform, log in to the:
Linux-based POA Management Node via SSH as root and go to the
"/usr/local/pem/bin/" directory OR
Windows-based POA Management Node via RDP as Administrator, open the
command prompt and go to the "C:\Program Files\SWsoft\PEM\bin\" directory
and execute:
VEM_ctl -f /usr/local/pem/etc/pleskd.props vz3_shared_ves_to_vz4 <hw_host_id> <hw_node_ip> <user> <password>
OR
VEM_Ctl.exe -f "C:\Program Files\SWsoft\PEM\properties"
vz3_shared_ves_to_vz4 <hw_host_id> <hw_node_ip> <user> <password> where
hw_host_id - The ID of VPS Hardware Node in POA. This ID can be obtained from the
list of VPS Hardware Nodes (Top > Service Director > Virtuozzo Manager > VPS Hardware
Nodes).
hw_node_ip - BackNet IP Address of VPS Hardware Node. This IP Address is used by
POA for managing the VPS Hardware Node.
user - The login of VPS Hardware Node administrator (root/Administrator) password - The password of VPS Hardware Node administrator
A
Activating Plesk Sitebuilder License • 104 Adding a Package • 110
Adding Account Information Into Header of E- mail Sent From Web Server • 69
Adding Attribute to Host • 129 Adding Hardware Node • 121 Adding IP Pool to Host • 118
C
Checking MySQL Databases on Service Node • 92
Common Operations • 106 Completing Upgrade • 96
Configuring Customer Backup Server • 68 Configuring Excluded File Extensions List •
82
Configuring Firewall • 107
Configuring IP Pool for WebSites With SSL Support • 20
Configuring Log Rotation • 83
Configuring Web Statistics Processor Server • 81
Configuring Web Statistics Retention Policy • 81
Copying Templates to PPM Mirror • 132 Creating Attributes • 123
Creating Certificate • 47
Creating Certificate Signing Request • 49 Creating 'Hardware Nodes' Resource Type •
120
Creating IP Pool • 117
Creating 'Shared VPSs BackNet IPs' IP Pool • 127
Creating 'Traffic' Resource Type • 120, 125 Creating VPS • 130
Creating 'VPS Hardware Nodes' Resource Type • 126
D
Deploying Apache Web Hosting • 9 Deploying Client Part • 72
Deploying Linux-based Database Hosting • 85 Deploying Mail Sender ID Server • 69
Deploying Parallels Plesk Sitebuilder for Linux/Unix • 100
Deploying WebsiteCreator Service • 58 Description • 73 Documentation Conventions • 6
F
Feedback • 8G
General Conventions • 8Generating Self-Signed Certificate • 48
H
Hardware Node Scenario • 19, 78
Hardware Requirements for Web Statistics Processor Server • 75
I
Importing Templates • 134
Installation Requirements • 18, 45, 53, 56, 61, 65, 98
Installation Requirements for Apache 2.0 • 14, 28
Installation Requirements for Apache 2.2 • 11, 25
Installation Requirements for Customer Backup Service • 67
Installation Requirements for Domain Parking Service • 39
Installation Requirements for MySQL 4 Service • 86
Installation Requirements for MySQL 5 Service • 89
Installation Requirements for VPS Backup Service • 68
Installation Requirements for Web Statistics Processor Server • 76
Installing a Package on the Host • 113 Installing Apache Web Server • 9 Installing Backup Service • 66
Installing CM4all WebsiteCreator Service • 58 Installing Domain Parking Service • 38 Installing FrontPage on Host • 17
Installing ionCube Loader and SQLite2 PHP Extensions • 17
Installing MySQL 4 • 85 Installing MySQL 5 • 88
Installing MySQL Service • 85
Installing osCommerce (Separate) • 60 Installing phpMyAdmin Service • 52 Installing phpPgAdmin Service • 55 Installing Plesk Sitebuilder • 102 Installing POA Packages • 19, 80, 103 Installing PostgreSQL Service • 97 Installing PPM Packages • 109 Installing RPM on Host • 131
Installing Service on Linux-based Host • 107 Installing SSL Proxy Server • 43
Installing Standard OS/Application Templates • 131
Installing Templates on Linux-based VPS Hardware Node • 136
Installing Templates on VPS Hardware Node • 135
Installing Templates on Windows-based VPS Hardware Node • 136
Installing Templates Using POA Control Panel • 132
Installing Templates Without Using POA Control Panel • 136
Installing Urchin Service • 64 Installing Web File Manager • 21
Installing Web Statistics Processor Server • 73
L
Legacy File Manager to Web File Manager Transition • 38
M
Marking Host as 'Ready To Provide' • 136
O
Obtaining URL to Template • 133
P
Preface • 6
Preparing Apache Web Servers for Site Publishing • 104
Prerequisites • 119, 124
Providing WebsiteCreator Resource • 59
R
Registering Linux-based Hardware Nodes • 119
Registering Linux-based VPS Hardware Nodes • 124
Registering Plesk Sitebuilder Servers in POA • 104
Registering VPS Hardware Node in POA • 129 Registering WebsiteCreator Server in POA •
59
Restarting Apache Service • 20
S
Setting Users Privileges • 101 Starting Upgrade • 95
Synchronizing VPS Hardware Node with World Time • 128
System Requirements • 100
System Requirements for Apache Web Servers • 9
System Requirements for Backup Servers • 66 System Requirements for Domain Parking
Server • 39
System Requirements for MySQL 4 Database Servers • 85
System Requirements for MySQL 5 Database Servers • 88
System Requirements for osCommerce Server • 60
System Requirements for phpMyAdmin Servers • 52
System Requirements for phpPgAdmin Servers • 55
System Requirements for PostgreSQL Database Servers • 97
System Requirements for SSL Proxy Server • 44
System Requirements for Urchin Server • 64 System Requirements for Web File Manager
Server • 23
T
Typographical Conventions • 6
U
Uninstalling Web Statistics Processor Server • 84
Updating Certificate • 51
Upgrading Linux/Windows VPS Hardware Node from PVC 3.x to PVC 4.x (Shared VPSs) • 137
Upgrading MySQL Database Server on Hardware Node • 93
Upgrading MySQL Database Server on VPS • 94
Upgrading MySQL PPM Package on Service Node • 97
Upgrading MySQL4 Database Servers to MySQL5 • 91
Upgrading Plesk Sitebuilder • 105
Upgrading Web Server from Apache 2.0 to Apache 2.2 • 33
Using VPS Hardware Node for Templates Import • 132
Viewing List of All MySQL4 Service Nodes • 91