Parallels

Resolution

Before upgrading make sure that old Parallels Plesk Sitebuilder functions normally.
If there were problems it is strongly not recommended to migrate. 

Here is schema of migration procedure.

1. Before starting upgrade on server with Parallels Plesk Sitebuilder 2.x backup database "sitebuilder", Sitebuilder home directory /usr/local/sitebuilder just in case;

2. Upgrade Sitebuilder packages 2.x to version 4.5 with Sitebuilder Autoinstaller.
Sitebuilder Autoinstaller script is available on Parallels website at http://www.parallels.com/download/sitebuilder4.

Note: if Sitebuilder 2.x is running on OS that is not supported by Sitebuilder 4.5 then intermediate upgrade to Sitebuilder 3 should be done. Here is schema:

1. Upgrade Parallels Plesk Sitebuilder 2.x to version 3.x and migrate sites on old OS
2. Upgrade OS to new version that is supported by Parallels Plesk Sitebuilder 4.5
3. Upgrade Parallels Plesk Sitebuilder 3.x to version 4.5 and migrate sites on new OS

 
Currently distributive of Parallels Plesk Sitebuilder 3.x is not available for downloading on Parallels website. Contact Parallels Support Team to provide assistance with migration.
 
3. All components should be upgraded. Use Autoinstaller to check the application is up-to-date. For example:


4. After the application is upgraded you may start sites migration to version 4.5.
Procedure of sites migration from version 2.x to 4.5 is performed in two phases. The first phase runs during packages upgrading.

Before starting second migration phase it is recommended to install hotfix sitebuilder45_migration_patch. 
The hotfix is in the attachment, download the file and upload it to Sitebuilder 4.5 server. To installing the hotfix move the file to root directory of Parallels Plesk Sitebuilder 4.5 (/usr/local/sitebuilder for RedHat-like OS, /opt/sitebuilder for Debian-like) and unpack it.  For example:


Then look into Sitebuilder migration log file. The file is located in directory /usr/local/sitebuilder/tmp and is called similar to sb_config-0905221243.log.

If the first migration phase finished successfully and no errors are shown in the log file, run the following command to start second migration phase:


If there are some errors in migration log, it is needed to repeat first and second migration phases. Run the following commands:


Where 2.1.3 is version of old Sitebuilder what is being migrated.

If the migration fail for some reason it is recommended to contact Parallels Support Team for assistance.

Additional information

NOTE: The instructions above are for upgrading of Parallels Plesk Sitebuilder within one server. If you want to migrate to another server it is recommended to upgrade Parallels Plesk Sitebuilder to version 4.5 on same server and then migrate. Refer to this article for details about migration of Parallels Plesk Sitebuilder 4.5 between severs: How to migrate sites and users to another Sitebuilder server?