Parallels® Plesk Control Panel
Copyright Notice
ISBN: N/A
Parallels
660 SW 39th Street
Suite 205
Renton, Washington 98057
USA
Phone: +1 (425) 282 6400
Fax: +1 (425) 282 6444
© Copyright 1999-2008,
Parallels, Inc.
All rights reserved
Distribution of this work or derivative of this work in any form is prohibited unless prior written
permission is obtained from the copyright holder.
Patented technology protected by U.S.Patents 7,328,225; 7,325,017; 7,293,033; 7,099,948;
7,076,633.
Patents pending in the U.S.
Product and service names mentioned herein are the trademarks of their respective owners.
Contents
Preface 8
About This Guide ........................................................................................................................... 8
Who Should Read This Guide ....................................................................................................... 8
Typographical Conventions ........................................................................................................... 8
Feedback ....................................................................................................................................... 9
About Plesk Migration Manager 10
Plesk Version-Specific Differences in Migration 12
Preparing for Migration 13
Preparing For Migration from Linux-Based Servers .................................................................... 13
Installing Migration Manager ............................................................................................. 14
Configuring Migration Manager ......................................................................................... 16
Restoring Default Configuration of Migration Manager ..................................................... 16
Preparing Servers For Migration ....................................................................................... 17
Configuring Firewall and Windows to Enable Migration .............................................................. 18
Preparing For Migration from Other Control Panels .................................................................... 21
Installing Migration Manager Components ....................................................................... 22
Configuring Migration Manager Components ................................................................... 29
Preparing Servers for Migration ........................................................................................ 38
Performing Migration 39
Performing Full Migration ............................................................................................................ 43
Performing Accounts Migration ................................................................................................... 45
Performing Domains Migration .................................................................................................... 49
Setting Up the Migration Preferences ......................................................................................... 54
Selecting Objects For Migration .................................................................................................. 55
Migrating Domains ............................................................................................................ 56
Migrating User Accounts ................................................................................................... 57
Selecting Target Client Account .................................................................................................. 59
Setting up IP Mapping ................................................................................................................. 60
Finishing Migration ...................................................................................................................... 61
Post-Migration Issues 63
Informing Customers of Migration Results .................................................................................. 64
Restoring File and Directory Attributes After the Migration ......................................................... 66
Viewing Migration Log ................................................................................................................. 66
Troubleshooting 69
Complying with Plesk Limits ........................................................................................................ 69
User Databases Migration ........................................................................................................... 70
Solving Problems With Site Applications Which Use Migrated Databases ...................... 71
Preface 4
Solving Problems With Migrating Databases to Plesk ...................................................... 72
Database Migration to Plesk 8.1.1 and Later Versions ..................................................... 75
Solving Problems With Accessing Domain Contents Through Shared SSL ............................... 76
Solving Problems With ODBC DSN Migration ............................................................................ 77
Solving Problems With Accessing Web Users Content .............................................................. 78
Solving Problems With Web Applications ................................................................................... 78
Solving Problems With Virtual Directories Content ..................................................................... 79
Solving Problems with Connectivity Between PMM Components .............................................. 79
Solving Problems With Migration of Domains, Subdomains, and Domain Aliases ..................... 80
Appendix 1. HELM Data Mapping Reference 83
Users Mapping ............................................................................................................................ 85
Client ................................................................................................................................. 86
Domain Administrator ........................................................................................................ 89
Templates Mapping ..................................................................................................................... 91
Client Templates Mapping ................................................................................................ 92
Domain Templates Mapping ............................................................................................. 94
Domains Mapping........................................................................................................................ 96
Limits ................................................................................................................................. 98
DNS Zone Settings ........................................................................................................... 99
Hosting Parameters .......................................................................................................... 99
Subdomains .................................................................................................................... 102
Mail .................................................................................................................................. 103
Databases ....................................................................................................................... 107
Protected URLs ............................................................................................................... 108
SSL Certificates............................................................................................................... 109
Additional FTP Accounts ................................................................................................. 110
Troubleshooting .............................................................................................................. 110
Appendix 2. Ensim 3.6 Pro Data Mapping Reference 111
Users Mapping .......................................................................................................................... 113
Client ............................................................................................................................... 114
Domain Administrator ...................................................................................................... 117
Web User ........................................................................................................................ 119
Templates Mapping ................................................................................................................... 119
Domains Mapping...................................................................................................................... 119
Web Site Content ............................................................................................................ 120
Hosting Parameters ........................................................................................................ 121
Limits ............................................................................................................................... 123
Subdomains .................................................................................................................... 124
DNS Zone Settings ......................................................................................................... 125
ODBC Data Source ......................................................................................................... 125
Domain Aliases ............................................................................................................... 127
Web Statistics.................................................................................................................. 128
MIME Types .................................................................................................................... 129
Databases ....................................................................................................................... 129
Log Rotation .................................................................................................................... 129
Anonymous FTP ............................................................................................................. 130
SSL Certificates............................................................................................................... 131
Shared SSL ..................................................................................................................... 131
Appendix 3. Ensim Pro 4.0, 5.0, and 10.x Data Mapping Reference 132
Users Mapping .......................................................................................................................... 134
Client ............................................................................................................................... 135
Domain Administrator ...................................................................................................... 139
Preface 5
Web User ........................................................................................................................ 141
Templates Mapping ................................................................................................................... 141
Client Templates Mapping .............................................................................................. 142
Domain Templates Mapping ........................................................................................... 144
Domains Mapping...................................................................................................................... 148
Web Site Content ............................................................................................................ 149
Hosting Parameters ........................................................................................................ 150
Limits ............................................................................................................................... 152
Subdomains .................................................................................................................... 154
DNS Zone Settings ......................................................................................................... 155
ODBC Data Source ......................................................................................................... 155
Domain Aliases ............................................................................................................... 157
Mail .................................................................................................................................. 157
MIME Types .................................................................................................................... 161
Web Statistics.................................................................................................................. 162
Databases ....................................................................................................................... 163
Log Rotation .................................................................................................................... 164
Anonymous FTP ............................................................................................................. 165
SSL Certificates............................................................................................................... 166
Shared SSL ..................................................................................................................... 166
Troubleshooting ......................................................................................................................... 167
Appendix 4. IIS 5.0 or 6.0 Data Mapping Reference 168
Control Panel-Independent Migration From IIS-Based Web Servers ....................................... 170
User Mapping ............................................................................................................................ 170
Security Policies ........................................................................................................................ 170
IP Address Mapping .................................................................................................................. 171
DNS Records ............................................................................................................................. 171
Databases ................................................................................................................................. 171
Web Statistics ............................................................................................................................ 171
E-mail services .......................................................................................................................... 171
Domains Mapping...................................................................................................................... 172
Domain Owners............................................................................................................... 173
Domain Certificates ......................................................................................................... 174
Domain Preferences ....................................................................................................... 174
Domain Aliases ............................................................................................................... 174
Standard Forwarding Mapping ........................................................................................ 175
Physical Hosting Mapping ............................................................................................... 175
Content Mapping ............................................................................................................. 180
Configuring Migration From IIS Manually ........................................................................ 182
Troubleshooting .............................................................................................................. 183
IIS Content and Services That Are not Migrated to Plesk .............................................. 184
Important IIS Server Settings That Are not Migrated to Plesk ........................................ 185
Appendix 5. Plesk For Unix Data Mapping Reference 186
Users Mapping .......................................................................................................................... 188
Client ............................................................................................................................... 188
Domain Administrator ...................................................................................................... 189
Web User ........................................................................................................................ 190
Templates Mapping ................................................................................................................... 190
Client Templates Mapping .............................................................................................. 191
Domain Templates Mapping ........................................................................................... 192
Domains Mapping...................................................................................................................... 194
Hosting Parameters ........................................................................................................ 194
Limits ............................................................................................................................... 195
Subdomains .................................................................................................................... 196
Preface 6
Mail .................................................................................................................................. 197
Appendix 6. cPanel and WHM Data Mapping Reference 198
Web Content, Mail, and Databases........................................................................................... 199
cPanel Object Mapping ............................................................................................................. 200
cPanel Objects That Are Subject to Migration and Their Plesk Counterparts ................ 201
cPanel Account Mapping ................................................................................................ 206
cPanel Domain Mapping ................................................................................................. 208
Migrated Plesk Object Mapping Reference ............................................................................... 213
Plesk Standard Forwarding Mapping .............................................................................. 215
Plesk Server Settings and Physical Hosting Mapping .................................................... 215
Important cPanel Settings That Are not Migrated to Plesk ....................................................... 242
cPanel Content and Services That Are not Migrated to Plesk ........................................ 242
WHM Settings That Are not Migrated to Plesk ............................................................... 243
Appendix 7. E-Mail Content Migration 244
Understanding Mail Migration .................................................................................................... 246
Getting List of E-Mail Accounts for Migration .................................................................. 247
Connecting to Source Mail Server .................................................................................. 248
Mail Migration Prerequisites ...................................................................................................... 249
Configuring Mail Servers to Enable Migration ........................................................................... 249
E-Mail Migration Tasks Supported by PMM .............................................................................. 250
Migrating Account Settings and E-Mail Content ............................................................. 251
Migrating Mail Content for Selected E-Mail Accounts ..................................................... 254
Migrating E-Mail Content to Existing E-Mail Accounts in Plesk ...................................... 255
Switching to Different Mail Server Application in Plesk .................................................. 256
Using Configuration File to Specify E-Mail Accounts for Migration ........................................... 257
When to Use Migration Configuration File ...................................................................... 261
When Not to Use Migration Configuration File ................................................................ 261
Using Configuration File to Support Migration From Non-Supported Mail Servers or UNIX-based
Mail Servers ............................................................................................................................... 262
Migrated Plesk Mail Data Mapping Reference .......................................................................... 263
Mail Servers Supported by PMM for Migration ............................................................... 265
Migration From MailEnable Mail Server .......................................................................... 265
Migration From SmarterMail Mail Server ........................................................................ 266
Migration From Merak Mail Server .................................................................................. 266
Migration From IMail Mail Server .................................................................................... 267
Migration From hMail Server ........................................................................................... 268
Migration From MDaemon Mail Server ........................................................................... 268
Migration From Communigate Pro Mail Server ............................................................... 269
Migration From Qmail Mail Server .................................................................................. 270
Troubleshooting ......................................................................................................................... 270
Appendix 8. User Databases and ODBC Data Sources Migration 272
Software Prerequisites for Database Migration ......................................................................... 273
Database Migration Basics ........................................................................................................ 274
Database Types Supported for Migration ....................................................................... 274
Database Migration From Remote Servers .................................................................... 275
Migration of ODBC DSN Records ................................................................................... 275
Database Names That Cannot Be Migrated ............................................................................. 276
Setting Up User Database Migration ......................................................................................... 277
Configuring Database Migration Manually ................................................................................ 280
Troubleshooting ......................................................................................................................... 282
Preface 7
Appendix 9. Migration from Plesk 284
Software Prerequisites .............................................................................................................. 284
Troubleshooting ......................................................................................................................... 285
Appendix 10. Domain DNS Zones Migration 286
DNS Servers Supported for Migration ....................................................................................... 287
Types of DNS Records Migrated to Plesk ................................................................................. 287
Using Plesk DNS Zone Template During Migration .................................................................. 288
IP Mapping During DNS Zones Migration ................................................................................. 288
Migration From Servers That Are not Supported by PMM for Migration ................................... 289
Configuring DNS Zones Migration Manually ............................................................................. 290
Troubleshooting ......................................................................................................................... 291
Appendix 11. FTP Content Migration 293
Understanding FTP Migration ................................................................................................... 294
FTP Servers Supported for Migration........................................................................................ 294
Migration From Servers That Are not Supported for Migration ................................................. 295
Modifying Configuration File to Enable Migration From Unsupported FTP Servers ....... 296
Customizing FTP Migration Process ......................................................................................... 297
Migrated FTP Data Reference .................................................................................................. 298
Migration From Microsoft FTP Server ............................................................................. 300
Migration From Serv-U FTP Server ................................................................................ 301
Migration From Gene6 Server......................................................................................... 302
Troubleshooting ......................................................................................................................... 303
Appendix 12. HELM 4 Data Mapping Reference 306
Preparing for Migration from Helm 4 ......................................................................................... 308
Specifying Database Services to Be Migrated ................................................................ 310
Helm 4 Object Subject to Migration and their Plesk Counterparts ............................................ 312
Helm 4 Account Mapping ................................................................................................ 315
Migrated Plesk Object Mapping Reference ............................................................................... 316
Plesk Client Account Mapping ........................................................................................ 318
Domain Templates Mapping ........................................................................................... 321
Domain Mapping ............................................................................................................. 322
Important Helm 4 settings that are not migrated to Plesk ......................................................... 338
Web Content ................................................................................................................... 338
Troubleshooting ......................................................................................................................... 339
Appendix 13. Ensim Pro for Linux Data Mapping Reference 342
Ensim Pro for Linux Objects Mapping ....................................................................................... 342
Migrated Plesk Objects Mapping Reference ............................................................................. 345
Plesk Users Mapping ...................................................................................................... 346
Domains Mapping ........................................................................................................... 353
Mail Mapping ................................................................................................................... 357
Databases ....................................................................................................................... 359
Important Ensim Pro for Linux Settings That Are Not Migrated to Plesk .................................. 361
Glossary 362
8 Preface
In this section:
About This Guide ............................................................................................... 8
Who Should Read This Guide ........................................................................... 8
Typographical Conventions ............................................................................... 8
Feedback .......................................................................................................... 9
Formatting
convention
Type of Information
Example
Special Bold
Items you must select,
such as menu options,
command buttons, or items
in a list.
Go to the System tab.
Titles of chapters, sections,
and subsections.
Read the Basic
Administration chapter.
Preface
About This Guide
This guide provides complete set of instructions on performing remote migration of hosted
data and mail content from different server management platforms to Plesk for Windows v.
7.5.6 - 8.6.
Who Should Read This Guide
This Guide is addressed to those who use hosting control panels other than Plesk and who
want to migrate
Typographical Conventions
Before you start using this guide, it is important to understand the documentation
conventions used in it.
The following kinds of formatting in the text identify special information.
Preface 9
Italics
Used to emphasize the
importance of a point, to
introduce a term or to
designate a command line
placeholder, which is to be
replaced with a real name
or value.
The system supports the
so called wildcard
character search.
Monospace
The names of commands,
files, and directories.
The license file is located
in the
http://docs/common
/licenses directory.
Preformatted
On-screen computer output
in your command-line
sessions; source code in
XML, C++, or other
programming languages.
# ls –al /files
total 14470
Preformatted
Bold
What you type, contrasted
with on-screen computer
output.
# cd
/root/rpms/php
CAPITALS
Names of keys on the
keyboard.
SHIFT, CTRL, ALT
KEY+KEY
Key combinations for which
the user must press and
hold down one key and
then press another.
CTRL+P, ALT+F4
Feedback
If you have found a mistake in this guide, or if you have suggestions or ideas on how to
improve this guide, please send your feedback using the online form at
http://www.parallels.com/en/support/usersdoc/. Please include in your report the guide‟s title,
chapter and section titles, and the fragment of text in which you have found an error.
Plesk Migration Manager is a tool for transferring hosting data from remote servers to
C H A P T E R 1
About Plesk Migration Manager
Plesk. At the present moment you can migrate your data from remote hosts where the
following hosting platforms, mail or database servers are installed:
Hosting Platforms
Helm, Version 3.1.x
Helm, Version 3.2.x
Helm, Version 4
Ensim Pro, Version 3.6, 4.0.1, 5, 10.x
Ensim Pro for Linux, Version 10.x
Plesk for Unix, Version 7.5 – 8.6
Plesk for Windows, Version 7.5 – 8.6
cPanel, Version 9, 10, 11
Web Servers
IIS, Version 5.0, 6.0
Plesk Migration Manager allows migrating user accounts, domains (including Web site
configuration and content, databases configuration and content, configuration of the
domain mail system, and so on) and objects similar to Plesk client and domain
templates. For the detailed information on the migrated data, refer to Data Mapping
Reference chapters that describe which objects of what hosting platform are migrated
to Plesk.
Mail Servers
Plesk Migration Manager supports mail migration from the following mail servers:
Mail Enable
Smarter Mail
Merak mail server (Windows)
hMail
MDaemon
IMail
Communigate Pro (Windows)
Qmail
About Plesk Migration Manager 11
Plesk Migration Manager can also migrate mail content from virtually any mail server
that supports POP3, IMAP4, or SMTP mail transfer protocols. For more details on mail
migration options, consult the “E-Mail Content migration” (on page 244) appendix.
Database Servers
Plesk Migration Manager supports migration of databases of the following types:
Microsoft SQL, Version 7.0, 2000, 2005
MySQL, Version 3.x-5.0.
ODBC DSN
For more details on databases migration options, consult the “User Databases and
ODBC Data Sources Migration” (see page 272) appendix.
DNS Servers
Microsoft DNS
Bind 8.x-9.x (Windows, UNIX)
Simple DNS Plus
For more details on DNS zones migration options, consult the “Domain DNS Zones
migration” (see page 286) appendix.
FTP Servers
Microsoft FTP
Serv-U
Gene6
For more details on FTP migration options, consult the “FTP Content migration” (see
page 293) appendix.
Plesk Migration Manager is produced for Plesk for Windows versions 7.5.6 - 8.6
Plesk version
PMM version-specific feature
Migrated parameter reference section
7.6 or later
Migration of FTP accounts from
Helm to Plesk
“Appendix 1. HELM Data Mapping
Reference” (on page 83) > “FTP
Subaccounts” (on page 110)
8.1 or later
PHP version support
“Appendix 1. HELM Data Mapping
Reference” (on page 83) > “Hosting
Parameters” (on page 99)
8.1.1 or later
Multiple SQL Server support
“Database Migration to Plesk 8.1.1 and
Later Versions” (on page 75)
C H A P T E R 2
Plesk Version-Specific Differences in
Migration
PMM available for a particular Plesk version will support migration of all features for all
platforms that can be migrated to Plesk. While most of the migrated parameters are the
same for different Plesk versions, the newer Plesk versions that have more features
have more parameters to be migrated.
The different Plesk version-specific PMM releases are available for download at the
Parallels (formerly SWsoft) web site.
The following table describes Plesk version-specific migration parameters.
This chapter answers the following questions:
In this chapter:
Preparing For Migration from Linux-Based Servers............................................13
Configuring Firewall and Windows to Enable Migration ................................ ......18
Preparing For Migration from Other Control Panels ...........................................21
In this section:
Installing Migration Manager ............................................................................. 14
Configuring Migration Manager ......................................................................... 16
Restoring Default Configuration of Migration Manager ...................................... 16
Preparing Servers For Migration........................................................................ 17
C H A P T E R 3
Preparing for Migration
How to install Migration Manager?
How to correctly configure Migration Manager components?
How to prevent possible conflicts?
Preparing For Migration from Linux-Based
Servers
This section explains in details the preparation procedure that should be carried out
before the actual data migration from other Plesk servers (for example, Plesk For
Linux/Unix servers).
Plesk Migration Manager supports migration from virtually all Linux platforms with Perl
5.0 and later, for example, Debian 3.1, Ubuntu 5.04, FreeBSD 4.9, FreeBSD 5.3,
CentOS 3.3, Fedora Core 1,2,3,4, Mandrake Linux 10.0, RedHat 7.3, RedHat 9,
RedHat EL 2,3,4, SuSE 9.1, 9.3.
14 Preparing for Migration
Installing Migration Manager
Run the installation file and follow the installation wizard instructions:
1 When the first screen of the installation wizard appears, click Next>. This starts the
Plesk Migration Manager installation.
Preparing for Migration 15
2 After Plesk Migration Manager is installed, click Finish to exit the installation wizard.
16 Preparing for Migration
Configuring Migration Manager
Before starting your first migration, you may want to prepare your Plesk server after the
Plesk Migration Manager is installed.
The most important condition of performing successful migration is that your Plesk
server should have a connection to the source Plesk server. The connection between
the source and the target Plesk servers is made through SSH. You need to have root
access in order to perform migration from Plesk for Linux/Unix.
If you need to change the name or location of the folder where the temporary dump will
be stored:
1 Open for editing the migrmng.exe.config file located in
%plesk_dir%\admin\bin\, where %plesk_dir% is the system
variable defining the folder where Plesk is installed.
To change the dump folder name - add the name into the „<add
key=”DumpName” value=”” />‟ string.
For example, if you want the migration dump folder to be named
“migration_data”, this string should be „<add key=”DumpName”
value=”migration_data” />‟. If such directory does not exist on disk H, it will be
created.
To change the dump folder location, add the full path (starting with the drive
root) to folder where it should be placed into the „<add key=”DumpDirectory”
value=”” />‟ string.
For example, if you want the migration dump folder named “migration_data” to
be stored in the folder H:\Store\Plesk_migration, this string should be
„<add key=”DumpDirectory” value=”H:\Store\Plesk_migration” />‟. In this case,
all migration data will be stored in
H:\Store\Plesk_migration\migration_data\.
To change the location of the dump folder on the remote server, add the full
path to the directory where it is to be placed into the „<add
key=”UnixDumpDirectory” value=”/usr/local” />‟ string.(/usr/local - is the default
value for the parameter). If the specified directory does not exist, it will be
created.
2 Save the file.
Restoring Default Configuration of Migration Manager
If the Migration Manager configuration file is corrupt, restore it as follows:
1 Delete the corrupt configuration file
%plesk_dir%\admin\bin\migrmng.exe.config.
2 Run the installation file pmm_buildXXXXXX.XX.msi.
3 In the installation wizard, select the Repair option, click Next>, and follow the wizard‟s
instructions.
Preparing for Migration 17
Preparing Servers For Migration
There are several operations you have to do before you start migrating hosting data
from your source Plesk server:
1 Make sure that the source server is available for connection with the target server
and that firewall on both servers is configured so that to allow this connection.
2 Make sure that both the source server and the target server have enough free disk
space for temporary migration files and the migration dump. To estimate how much
free space you need, consider the amount of disk space used by databases and
domain content folders.
3 MySQL user‟s databases used on the source server domains can be successfully
migrated to Plesk for Windows on the following conditions:
On the source server side, a connection should be established to MySQL server
with the parameters defined in the configuration of the source Plesk server.
User account defined in the configuration of this connection should have the
rights on all user‟s databases that will be migrated.
On the target server side, the connection to MySQL server should be configured
in Plesk, and this connection should be established during the migration.
4 Make sure the SSH banner is disabled on the source server.
To disable the SSH banner, open the /etc/ssh/sshd_config file, find the
Banner <path> line and transform it into comment by putting the # sign in front of
it:
# Banner <path>
18 Preparing for Migration
Configuring Firewall and Windows to
Software
Port
Protocol
SAMBA
135
TCP
139
TCP
445
TCP
137
UDP
138
UDP
PMM
6489 (or other)
TCP
SHH
22 (or other)
TCP
Enable Migration
If the Plesk server is behind a firewall, you need to properly configure the firewall to
allow the migration data exchange between the Migrator and the Migration Agent.
The following conditions must be observed:
Ports (with specific protocols enabled) required by SAMBA and Plesk Migration
Manager are opened.
The Client for Microsoft Networks and the File and Printer Sharing for Microsoft
Networks Windows applications are installed.
The Workstation service must be running on the Plesk server.
The Server service must be running on the remote server.
Administrative shares (admin$, c$, d$) must exist on the remote server.
In this topic:
Opening ports for SAMBA and PMM
Checking if the Client for Microsoft Networks and the File and Printer Sharing for
Microsoft Networks Windows applications are installed
Installing Client for Microsoft Networks
Installing File and Printer Sharing for Microsoft Networks
Opening ports for SAMBA, SSH and PMM
When you are migrating from Linux/UNIX-based servers, PMM uses SSH for network
connections. For migration from a Windows-based server, PMM uses SAMBA. SSH,
SAMBA, and the PMM require that certain ports are opened to enable proper network
connectivity for migration.
Specifically, the following ports must be open and the data exchange protocols enabled
on the ports.
Preparing for Migration 19
Checking if the Client for Microsoft Networks and the File and Printer Sharing for
Microsoft Networks Windows applications are installed
To verify that the software packages are installed, follow these steps:
1 Open Local Area Connection window (On the Start menu, select Control Panel > Network
Connections > Local Area Connection). The Local Area Connection Status window opens.
2 In the Local Area Connection Status window, select the the General tab and click the
Properties button. The Local Area Connection Properties window opens.
3 In the Local Area Connection Properties window, under This connection uses the following
items, check that the Client for Microsoft Networks and the File and Printer Sharing
for Micrrosoft Networks applications are listed and make sure that the
corresponding check boxes on the left are selected.
Installing Client for Microsoft Networks
To install Client for Microsoft Networks, follow these steps:
1 Open Local Area Connection window (On the Start menu, select Control Panel > Network
Connections > Local Area Connection). The Local Area Connection Status window opens.
2 In the Local Area Connection Status window, select the the General tab and click the
Properties button. The Local Area Connection Properties window opens.
3 Click the Install button. The Select Network Component Type window opens.
4 Under Click the type of network component you want to install, click Client. The Select
Network Client window opens.
5 In the list of network clients, select Client for Microsoft Networks and click OK.
6 Once the application is installed, the Client for Microsoft Networks item appears in the
Local Area Connection Properties window, under This connection uses the following items.
7 Select Client for Microsoft Networks by using the corresponding check box on the left.
20 Preparing for Migration
Figure 1: Installing Client for Microsoft Networks
Note: You must restart Windows for the configuration changes to take effect.
Installing File and Printer Sharing for Microsoft Networks
To install File and Printer Sharing for Microsoft Networks, follow these steps:
1 Open Local Area Connection window (On the Start menu, select Control Panel > Network
Connections > Local Area Connection). The Local Area Connection Status window opens.
2 In the Local Area Connection Status window, select the the General tab and click the
Properties button. The Local Area Connection Properties window opens.
3 Click the Install button. The Select Network Component Type window opens.
4 Under Click the type of network component you want to install, click Service. The Select
Network Service window opens.
5 In the list of network clients, select File and Printer Sharing for Microsoft Networks and
click OK.
Preparing for Migration 21
6 Once the application is installed, the File and Printer Sharing for Microsoft Networks item
In this section:
Installing Migration Manager Components ........................................................ 22
Configuring Migration Manager Components .................................................... 29
Preparing Servers for Migration ......................................................................... 38
appears in the Local Area Connection Properties window, under This connection uses the
following items.
7 Select File and Printer Sharing for Microsoft Networks by using the corresponding check
box on the left.
Note: You must restart Windows for the configuration changes to take effect.
Preparing For Migration from Other
Control Panels
This section explains in details the preparation procedure that should be carried out
before the actual data migration from other control panels (for example, Ensim Pro,
cPanel). If you are migrating from Helm 4, you should also see the “Preparing for
Migration” (on page 308) section in Appendix 12. “Helm 4 Data Mapping Reference”
(on page 306).
22 Preparing for Migration
Installing Migration Manager Components
In this section:
Installing Migration Manager ............................................................................. 23
Installing Migration Agent .................................................................................. 25
Plesk Migration Manager consists of the following two components:
1 Plesk Migration Manager - should be installed on the server with Plesk where you
want to migrate your hosting data.
2 Plesk Migration Agent - should be installed on the remote server from which you
want to migrate data.
These components are available for downloading at the Parallels (formerly SWsoft)
official site at the Download Plesk for Windows page. When the page opens, scroll
down to locate the list of utilities for your version of Plesk for Windows, then, follow the
Plesk Migration Manager and Plesk Migration Agent download links in the Migration
Utilities section.
Note: Install Plesk Migration Manager components from one package. Otherwise,
migration will fail.
After you have installed Plesk Migration Manager components, you can configure them
and start migrating your hosted data to Plesk.
Preparing for Migration 23
Installing Migration Manager
Run the installation file and follow the installation wizard instructions:
1 When the first screen of the installation wizard appears, click Next>. This starts the
Plesk Migration Manager installation.
24 Preparing for Migration
2 After Plesk Migration Manager is installed, click Finish to exit the installation wizard.
Preparing for Migration 25
Installing Migration Agent
Run the Migration Agent installation file and follow the installation wizard instructions:
1 When the first screen of the installation wizard appears, click Next>. This starts the
Plesk Migration Agent installation.
26 Preparing for Migration
2 Enter your personal information next to Full Name and Organization, and define the
usage policy for Plesk Migration Agent by selecting whether any user or only you
can use Plesk Migration Agent. Click Next>.
Preparing for Migration 27
1. To install Plesk Migration Agent files to the default location C:\Program
Files\Parallels\Plesk Migrator Agent\, click Next>.
To specify another location, click Browse and select the desirable folder. Click
Next>.
28 Preparing for Migration
2. To change installation properties, click <Back.
To start installation of Migration Agent with specified settings, click Next>.
Preparing for Migration 29
3 After the installation wizard has installed Migration Agent files to your server, click
Finish.
Once you have installed Migration Agent, it starts automatically with the default settings
(see page 29).
Configuring Migration Manager Components
Before starting your first migration, you may want to prepare Plesk server and source
server after the Plesk Migration Manager components are installed.
The most important condition of performing successful migration is that Plesk server
should have a connection to source server. This connection is established by Plesk
Migration Manager, which is installed on the Plesk server, and Plesk Migration Agent,
which is installed on the source server.
This connection is established if the following settings of Migration Agent configurations
on the source server and on Plesk server match:
Port - number of the port that is used by Plesk for connecting to Migration Agent.
(Default is 6489.)
To specify the port correctly, consider the following:
It can be any number from 1 to 65535.
It must be free on server from which data will be migrated, that is, this port
should not be used by any other programs or services on both servers.
It must be allowed by firewall on server from which data will be migrated.
Migration Agent URI - name of the system object used by Plesk for calling Migration
Agent. (Default is “WinAgentURI”.)
To specify the Migration Agent URI correctly, consider the following
It can contain only numbers, and Latin letters of upper and/or lower case.
It should not be used by another application on server from which data will be
migrated.
Channel type - the way of Migration Manager and Migration Agent connection.
(Default is HTTP.)
When selecting the channel type, consider the following characteristics:
TCP provides better performance than HTTP
HTTP is more public as it uses HTTP protocol, which is allowed by most of
firewalls.
Note: If these connection parameters are not the same in Plesk Migration Manager
configurations on Plesk server and source server, you will be unable to perform
migration.
Migration Manager configuration also contains parameters that define the location and
the name of migration dump. It is a folder containing all data of the objects selected for
migration. Migration dump is created on the source host during the migration process,
then it is transferred to Plesk server and the hosting data is imported to Plesk.
30 Preparing for Migration
By default, migration dump is created with the name “Main” in the %TEMP%\migrator
In this section:
Editing Configuration of Migration Manager Components on Plesk Server ........ 31
Editing Migration Agent Configuration on Source Server ................................... 34
Restoring Default Configuration of Migration Manager Components ................. 37
backup folder (where %TEMP% is environment variable defining the temporary folder of
the currently logged user). When the dump is transferred to Plesk server, it is placed to
%plesk_dir%\PMM\Store by default.
You have an ability to change these default names and locations when editing Plesk
Migration Manager components configurations.
Note: It is recommended that you do not change the default configuration of Migration
Agent unless necessary, in order to prevent configuration files corruption. Such cases
of necessity are, for example, security reasons or resolution of conflicts that may
appear in the system.
Preparing for Migration 31
Editing Configuration of Migration Manager Components on
Plesk Server
The Migration Agent configuration settings are stored in the migrmng.exe.config file.
After installing Migration Manager on Plesk server, you can:
Change settings of the Migration Manager connection with Migration Agent (port,
Migration Agent URI and channel type).
Specify where on Plesk server and under what name a migration dump folder
should be created. This is necessary if, for example, there is not enough disk space
on the disk where Plesk is installed.
To perform any of these actions:
1 Open for editing the migrmng.exe.config file located in
%plesk_dir%\admin\bin\, where %plesk_dir% is the system variable defining
the folder where Plesk is installed.
Here are the contents of the configuration file with default settings:
<?xml version=”1.0” encoding=”utf-8” ?>
<configuration>
<configSections>
<section name=”Platforms”
type=”ForeignMigratorEngineCore.Configuration.PlatformsSectionHa
ndler,ForeignMigratorEngineCore”/>
</configSections>
<startup>
<supportedRuntime version = “v2.0.50727” />
<supportedRuntime version = “v1.1.4322” />
</startup>
<appSettings>
<add key=”Port” value=”6489” />
<add key=”ObjectUri” value=”WinAgentURI” />
<add key=”ChannelType” value=”HTTP” />
<add key=”DumpDirectory” value=”” />
<add key=”DumpName” value=”” />
<add key=”UnixDumpDirectory” value=”/usr/local” />
<add key=”LogUseDefaultCulture” value=”false” />
<add key=”SSHTimeout” value=”300” />
</appSettings>
<Platforms>
...
</Platforms>
32 Preparing for Migration
</configuration>
The Platform element contains migration configuration data for all platforms
supported for migration. You can manually configure specific platform migration
sections to configure the migration process. For detailed information about
configurable migration options available for a specific platform, see the section
describing manual configuration of the migration configuration file in the
corresponding appendix.
Warning: Do not change or move the configSections element from the default
location. Also, we recommend that you do not change anything enclosed with the
<startup> tag, as doing this can crash Migration Manager.
2 To make changes to the configuration file, enter the required value in an
appropriate string instead of the default one:
To configure connection to Migration Agent:
To change port number - in the <add key=”Port” value=”6489” />
string instead of “6489” (omitting quotation marks).
For example, if you want port 7788 to be used, this string should be <add
key=”Port” value=”7788” />.
To change Migration Agent URI - in the <add key=”ObjectUri”
value=”WinAgentURI” /> string instead of “WinAgentURI” (omitting
quotation marks)
For example, if you want “MigrationAgent325” to be used as the Migration
URI, this string should be <add key=”ObjectUri”
value=”MigrationAgent325” />.
To change channel type - in the <add key=”ChannelType”
value=”HTTP” /> instead of “HTTP” (omitting quotation marks).
For example, if you want to use TCP, this string should be <add
key=”ChannelType” value=”TCP” />.
To change the default name and location of migration dump:
To change the dump folder name - add the name into the <add
key=”DumpName” value=”” /> string.
For example, if you want the migration dump folder to be named
“migration_data”, this string should be <add key=”DumpName”
value=”migration_data” />. If such directory does not exist on disk H,
it will be created.
To change the dump folder location, add the full path (starting with the drive
root) to folder where it should be placed into the <add
key=”DumpDirectory” value=”” /> string.
For example, if you want the migration dump folder named “migration_data”
to be stored in folder H:\Store\Plesk_migration, this string should be
<add key=”DumpDirectory”
value=”H:\Store\Plesk_migration” />. In this case, all migration
data will be stored in H:\Store\Plesk_migration\migration_data\.
Preparing for Migration 33
To change the maximum time of SSH session without the server response,
after which the session is closed, add the time period in seconds into the
<add key=”SSHTimeout” value=”” /> string.
For example, if you want to set the maximum time of SSH session without
the server response to 600 seconds, this string should be <add
key=”SSHTimeout” value=”600” />.
3 Save the file and proceed to editing Migration Agent Configuration on source
server, described in the next section.
34 Preparing for Migration
Editing Migration Agent Configuration on Source Server
After installing Migration Agent on source server, you can:
Change settings of the Migration Agent connection with Migration Manager (port,
Migration Agent URI and channel type).
This can be done using either Migration Agent interface or Migration Agent
configuration file.
Specify where on source server a migration dump file should be created. This is
necessary if, for example, there is not enough disk space on the disk where
Migration Agent is installed.
Changing parameters of Migration Manager components connection via Migration
Manager interface
1 Run the WINAgentMng.exe file. The Migration Manager window opens.
Figure 2: Plesk Migration Agent window
If Migration Agent was installed in the default location, you can access it by clicking
Start > Programs > Parallels > Plesk > Plesk Migration Agent, or browsing for
C:\Program Files\Parallels\Plesk Migration
Agent\WINAgentMng.exe.
2 Click Stop. This makes changing Migration Agent settings available.
Figure 3: Plesk Migration Agent stopped: changing settings is available
3 To change the port number, enter the desirable value next to Port.
4 To change Migration Agent URI and channel type:
1. Click Advanced. The advanced options window opens.
Preparing for Migration 35
Figure 4: Plesk Migration Agent: advanced options
2. To change Migration Agent URI, enter desirable name next to URI.
3. To set up a channel type, select an appropriate item in the Channel Type menu.
4. Click OK. This applies the changes made to advanced options and closes the
advanced options window.
5 Click Start. This applies changes made to the port number and starts Migration
Agent with new settings.
Editing Migration Agent Configuration File
You can edit the Migration Agent configuration settings manually. For the changes to
take effect after manual editing, you must restart the Migration Agent application on the
remote machine.
To configure connection between Migration Manager and Migration Agent using
configuration file and to specify the desirable location of migration dump, do the
following:
1 Open for editing the %Plesk Migration Agent%\WINAgentMng.exe.config
file (%Plesk Migrator Agent% is a system variable defining where Plesk
Migration Agent is installed).
Here are the contents of the configuration file with default settings:
<?xml version=”1.0” encoding=”utf-8” ?>
<configuration>
<startup>
<supportedRuntime version = “v2.0.50727” />
<supportedRuntime version = “v1.1.4322” />
</startup>
<system.runtime.remoting>
<customErrors mode=”off” />
<application name=”Parallels Foreign Migration Agent” />
</system.runtime.remoting>
36 Preparing for Migration
<runtime>
<assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1”>
<probing privatePath=”bin”/>
</assemblyBinding>
</runtime>
<appSettings>
<add key=”Port” value=”6489” />
<add key=”ObjectUri” value=”WinAgentURI” />
<add key=”ChannelType” value=”HTTP” />
<add key=”IPAddress” value=”” />
<add key=”DumpDirectory” value=”” />
</appSettings>
</configuration>
To make changes to the configuration file, enter the required value in an
appropriate string instead of the default one.
Note: It is strongly recommended that you do not change anything enclosed with
the <system.runtime.remoting>, <startup>, and <runtime> tags, as doing
this can crash Migration Manager.
2 To change connection parameters:
to change port number - in the <add key=”Port” value=”6489” /> string
instead of “6489” (omitting quotation marks).
For example, if you want port 7788 to be used, this string should be <add
key=”Port” value=”7788” />.
to change Migration Agent URI - in the <add key=”ObjectUri”
value=”WinAgentURI” /> string instead of “WinAgentURI” (omitting
quotation marks).
For example, if you want “MigrationAgent325” to be used as the Migration URI,
this string should be <add key=”ObjectUri”
value=”MigrationAgent325” />.
to change channel type - in the <add key=”ChannelType” value=”HTTP”
/> instead of “HTTP” (omitting quotation marks).
For example, if you want to use TCP, this string should be <add
key=”ChannelType” value=”TCP” />.
To change the Migration Agent‟s IP address, enter the IP address value for the
corresponding key in the string <add key=”IPAddress” value=”” />. This will
enable PMM to connect with Migration Agent through the entered IP address
only. Type “0.0.0.0” or remove the string from the file altogether to enable
PMM to connect with Migration Agent through any IP address available on the
machine where Migration Agent is installed.
Preparing for Migration 37
To change the dump location, add the full path (starting with the drive root) to folder
where the file should be stored into the <add key=”DumpDirectory”
value=”” /> string.
For example, if you want the migration dump to be stored in folder
H:\Store\Plesk_migration, this string should be <add
key=”DumpDirectory” value=”H:\Store\Plesk_migration” />. If
such directory does not exist on disk H, it will be created.
3 Save file.
4 Restart the Migration Agent application.
Restoring Default Configuration of Migration Manager
Components
If any of the configuration files (either on Plesk server or remote server) is corrupt,
restore it as follows:
1 Delete the corrupt file.
If the Migration Agent configuration on source server is corrupt, delete the
%Plesk Migration Agent%\WINAgentMng.exe.config file.
If the Migration Manager configuration on Plesk server is corrupt, delete the
%plesk_dir%\admin\bin\migrmng.exe.config file.
2 Run the installation file:
pmm_agent_buildXXXXXX.XX.msi, on source server
pmm_buildXXXXXX.XX.msi, on Plesk server.
3 In the installation wizard, select the Repair option, click Next>, and follow the wizard‟s
instructions.
38 Preparing for Migration
Preparing Servers for Migration
There are several operations you have to do before you start migrating hosting data
from your source server to Plesk server:
1 Make sure that Migration Agent is running on the server from which you want to
migrate your data, and that it is started.
When Plesk Migration Agent is running, its icon is shown in system tray indicating
the agent state:
- started
- stopped
If Migration Agent is not running, click Start > Programs > Parallels > Plesk > Plesk
Migration Agent. It will be started.
If Migration Agent is running, but it is stopped, start it by right-clicking the Agent‟s
icon in system tray and selecting Start in the menu, or by double-clicking the icon
and clicking on Start button in the Agent‟s window.
2 Make sure that the source server is available for connection with Plesk server and
that firewall on both servers is configured so that to allow this connection.
3 Make sure that both the source server and Plesk server have enough free disk
space for temporary migration files and the migration dump. To estimate how much
free space you need, consider the amount of disk space used by databases and
domain content folders.
4 MySQL user‟s databases used on the source server domains can be successfully
migrated to Plesk on the following conditions:
On the source server side, a connection should be established to MySQL server
with the parameters defined in the configuration of the source hosting panel.
User account defined in the configuration of this connection should have the
rights on all user‟s databases that will be migrated.
On the Plesk server side, the connection to MySQL server should be configured
in Plesk, and this connection should be established during the migration.
5 Microsoft SQL Server user‟s databases used on the source server domains can be
successfully migrated to Plesk on the following conditions:
On the source server side, a connection should be established to local Microsoft
SQL Server configured in the source hosting panel, and this connection should
be established during the migration. User account defined in the configuration of
this connection should have the rights on all user‟s databases that will be
migrated.
On the Plesk server side, the connection to local Microsoft SQL Server should
be configured in Plesk, and this connection should be established during the
migration.
Types of Migration
C H A P T E R 4
Performing Migration
Migration Manager allows performing the following types of migration:
Full migration - migrating all user accounts, domains, and objects that can be
mapped to Plesk domain and client templates.
Accounts migration - migrating selected user accounts (including all domains
registered within those accounts).
Domains migration - migrating selected domains to the specified Plesk client
account.
Starting Migration
To start a migration of any type, follow these steps:
1 Access Plesk Migration Manager:
1. Log in to Plesk as Administrator.
2. Click the Server shortcut in the navigation pane, and then click Migration
Manager located under Services. This opens the first page of Migration Manager
wizard:
Figure 5: Migration Manager wizard: setting up connection to source server
2 Establish connection to the remote host from which you wish to migrate data to
your Plesk server:
40 Performing Migration
1. Enter the remote server name or IP address into the Source host text input field.
Note: For migration from UNIX-based platforms only, you can indicate a port to be
used for SHH connection, for example, 10.64.127.62:8022. If you do not specify
the port at this step, port 22 will be used for SHH connection by default.
2. Enter login and password for logging in to the source host into the
corresponding fields.
Note that the login and password you specify on this step must be credentials of
the remote host user account with administrator‟s privileges.
3. Select operating system running on the remote host next to OS type.
4. Click Next>>.
After this, Plesk Migration Manager connects to the specified remote server.
Note: If you are performing migration from control panels other than Plesk, make sure
that Migration Agent is installed on the source host (refer to the Preparing For Migration
from Other Control Panels (on page 21) section for more information).
If the connection is successfully established, Plesk Migration Manager determines the
source hosting platform, the migration starts and you proceed to the next step. On this
step, Migration Manager shows the page displaying the source host information and
allowing to set up the migration preferences:
Migration Manager provides you with the following information on the selected source
host:
Source hosting platform - hosting platforms supported by Plesk Migration Agent that
were detected on the remote host.
Figure 6: Plesk Migration Manager wizard: setting up migration preferences
Performing Migration 41
„Hosting platform‟ here means the way that data related to hosting is organized. If
there is HELM installed on the remote server, you always see 2 hosting platforms
(Resellers and Users), which conceive two ways of migrating data (mapping HELM
Reseller accounts to Plesk Client accounts or HELM User accounts to Plesk Client
accounts). If Ensim Pro is installed on the remote server, only one hosting platform
(Ensim) is displayed.
Average CPU load - average CPU usage on the remote host.
When the source hosting platform is Unix, Average CPU load field will show you three
numbers, displaying average CPU load during the last 1, 5 and 15 minutes
respectively. If this value is too high, the migration can take longer.
Operating system - the detailed info on the operating system installed on the remote
server.
Plesk Migration Manager allows you to choose between two types of migration:
Selective Migration, when only the objects of your selection are migrated, and Full
Migration, when all objects are migrated. How to perform migration of each type is
described in the following subsections.
Continuing Interrupted Migration Process
The migration process is interrupted if you leave the Migration Manager wizard on any
step after the migration has been started before it is completed. You leave the
Migration Manager wizard if you go to another Plesk page, log out from Plesk or close
your Web browser window with Plesk session.
Plesk Migration Manager protects you from losing migration data: if a migration is
interrupted, Migration Manager saves all the information on this migration, and will offer
you to continue it the next time you access Migration Manager:
Figure 7: Plesk Migration Manager: offer to continue interrupted migration
To continue the interrupted migration, select the Continue migration option and click OK.
Migration Manager will open page of the migration step on which the migration was
interrupted.
Stopping Migration
42 Performing Migration
Stopping migration cancels the migration. If you stop the migration, Migration Manager
In this chapter:
Performing Full Migration .................................................................................. 43
Performing Accounts Migration.......................................................................... 45
Performing Domains Migration .......................................................................... 49
Setting Up the Migration Preferences ................................................................ 54
Selecting Objects For Migration......................................................................... 55
Selecting Target Client Account ........................................................................ 59
Setting up IP Mapping ....................................................................................... 60
Finishing Migration ............................................................................................ 61
will “forget” about it and won‟t offer you to continue it.
You can stop migration by clicking Cancel on the following Migration Manager steps:
Selecting Objects for Migration
Selecting Target Client Account
Mapping Remote Host IPs to Existing
Doing this takes you to the Stopping Migration page. Select the Remove archive check box
to remove any temporary files created during the migration, and click OK.
Performing Migration 43
Performing Full Migration
Specifying the Migration Preferences
1 On the Migration Preferences page, select the Full migration option under Migration
type:
Figure 8: Migration Preferences: selecting Full migration
2 Select the source hosting platform that must be used during the migration if there
are several platforms on the source server.
3 Click Next>> to proceed to the IP mapping configuration.
Setting up IP Mapping
On this step, you should configure IP mapping settings for the migration, that is, you
have to choose which Plesk IP addresses must be used for the remote host objects
when the migration is completed. This is the final step of Migration Manager wizard:
once you click Next>> on this page, transferring the data will start.
44 Performing Migration
Figure 9: Performing Full migration: setting up IP mapping
This page shows the list of all remote host IP addresses assigned to objects that were
selected for the migration. Columns in the list provide the following information:
T (type) - indicates the IP address type:
- exclusive IP address (can be assigned only to one client).
- shared IP address (can be assigned to many clients).
Source IP Address - IP assigned to an object in the source hosting platform.
Destination IP - each line is a list of IP addresses registered in Plesk. The IPs that
are not assigned to any Plesk client are listed under Vacant IP Addresses. The list
contains all shared IP addresses registered in Plesk and vacant exclusive IP
addresses.
Before you perform IP mapping, it is important to keep the following in mind:
Shared source IPs can be mapped only to shared destination IPs.
Exclusive source IPs can be mapped either to vacant exclusive destination IPs or to
shared destination IPs, if there‟s not enough vacant exclusive IPs present in Plesk.
Several source IPs belonging to Ensim Pro IP-based sites can be mapped to one
exclusive IP address in Plesk. It is advised to use this capability with caution,
though, as allocating several migrated domains on one exclusive Plesk IP can
cause problems with some of the domain settings such as Anonymous FTP.
To perform mapping:
Performing Migration 45
1 For each Source IP Address in the list, select a Destination IP from the corresponding
list in the Destination IP column.
2 Click Next>>. This starts transferring data to Plesk.
If there are not enough destination IPs, you can register new IP addresses in Plesk
as follows:
1 Click IP addresses located in the Tools group. Doing this takes you to the IP
addresses management page.
2 To register new IP, click Add New IP Address. Adding IP address page opens.
On that page, enter the data necessary for creating an IP address in Plesk and click
OK.
When you are finished with adding IP addresses to Plesk, click OK or Up Level on the IP
addresses management page. This takes you back to the Migration Manager page of
setting up IP mapping.
Performing Accounts Migration
Specifying the Migration Preferences
1 On the Migration Preferences page, select the Selective migration option under
Migration type:
Figure 10: Plesk Migration Manager wizard: setting up migration preferences
2 Select source hosting platform that must be used during the migration if there are
several platforms on the source server.
3 Click Next>> to proceed to selecting accounts for migration.
46 Performing Migration
Selecting Accounts for Migration
On this step, you should select the user accounts you want to migrate. For this, select
the Accounts tab:
Figure 11: Migration Manager wizard: selecting user accounts for migration
This page shows the list of all user accounts existing on the source server. Columns in
the list provide the following information:
S (status) - indicates account status in the scope of comparison to the list of
accounts existing on Plesk server:
- user account with such login does not exist in Plesk: it can be migrated to
Plesk, including all domains registered within this account in the source hosting
platform
- some names of the domains registered within this account match the
domain names existing in Plesk: the account itself and the rest of its domains
can be migrated to Plesk
- all names of the domains registered within this account match the domain
names existing in Plesk: only the account data can be migrated to Plesk
- user account with such login exists in Plesk: it cannot be migrated to Plesk
Login - login of the user‟s account
Client’s Name - real name of the account user
Number of domains - number of domains registered within this account in the source
hosting platform
Performing Migration 47
To define the accounts for migration:
1 Select check boxes next to the accounts you want to migrate.
To migrate all accounts, select the upper check box.
2 Click Next>> to proceed to the IP mapping configuration.
Setting up IP Mapping
On this step, you should configure IP mapping settings for the migration, i.e. you have
to choose which Plesk IP addresses must be used for the remote host accounts when
the migration is completed. This is a final step of Migration Manager wizard: once you
click Next>> on this page, transferring the data will start.
Figure 12: Performing Accounts migration: setting up IP mapping
This page shows the list of all remote host IP addresses assigned to user accounts that
were selected for the migration. Columns in the list provide the following information:
T (type) - indicates the IP address type:
- exclusive IP address (can be assigned only to one client)
- shared IP address (can be assigned to many clients)
Source IP Address - IP assigned to an object in the source hosting platform
Destination IP - each line is a list of IP addresses registered in Plesk. The IPs that
are not assigned to any Plesk client are listed under Vacant IP Addresses. The list
contains all shared IP addresses registered in Plesk and vacant exclusive IP
addresses.
48 Performing Migration
Before you perform IP mapping, it is important to keep the following in mind:
Shared source IPs can be mapped only to shared destination IPs.
Exclusive source IPs can be mapped either to vacant exclusive destination IPs or to
shared destination IPs, if there‟s not enough vacant exclusive IPs present in Plesk.
Several source IPs belonging to Ensim Pro IP-based sites can be mapped to one
exclusive IP address in Plesk. It is advised to use this capability with caution,
though, as allocating several migrated domains on one exclusive Plesk IP can
cause problems with some of the domain settings such as Anonymous FTP.
To perform mapping:
1 For each Source IP Address in the list, select a Destination IP from the corresponding
list in the Destination IP column.
2 Click Next>>. This starts transferring data to Plesk.
If there are not enough destination IPs, you can register new IP addresses in Plesk
as follows:
1 Click IP addresses located in the Tools group. Doing this takes you to the IP
addresses management page.
2 To register new IP, click Add New IP Address. Adding IP address page opens.
On that page, enter the data necessary for creating IP address in Plesk and click
OK.
3 When you are finished with adding IP addresses to Plesk, click OK or Up Level on
the IP addresses management page. This takes you back to the Migration Manager
page of setting up IP mapping.
Performing Migration 49
Performing Domains Migration
Specifying the Migration Preferences
1 On the Migration Preferences page, select the Selective migration option under
Migration type:
Figure 13: Plesk Migration Manager wizard: setting up migration preferences
2 Select source hosting platform that must be used during the migration if there are
several platforms on the source server.
3 Click Next>> to proceed to selecting domains for migration.
Figure 14: Plesk Migration Manager wizard: setting up migration preferences
50 Performing Migration
Selecting Domains for Migration
On this step, you should select the domains you want to migrate. For this, select the
Domains tab:
Figure 15: Plesk Migration Manager wizard: migrating domains
This page shows the list of all domains existing on the source server. Columns in the
list provide the following information:
S (status) - indicates domain status in the scope of comparison to the list of
domains existing on Plesk server:
- domain with such name does not exist in Plesk, and is available for
migration
- domain with such name exists in Plesk: it cannot be migrated
Name - domain name
Login - login of the user‟s account within which the domain is created
To define the domains you want to migrate:
1 Select check boxes next to the domains you want to migrate.
To migrate all domains, select the upper check box.
2 Click Next>> to proceed to selecting target client account.
Performing Migration 51
Selecting Target Client Account
On this step, you should define the Plesk client account to which you wish to migrate
the selected domains, that is, you should choose an account of a client who will be the
owner of the migrated domains.
This page shows the list of all client accounts existing in Plesk. Columns in the list
provide the following information:
P (problem) - indicates the state of client‟s domain(s):
- resource usage of client domains is within the defined limits
- disk space and/or traffic limitations are exceeded at the client domains
S (status) - indicates the client account status in the system:
- account is active
- account is disabled
Client name - real name of the client
Company name - name of the company specified in client‟s personal information
Creation date - date of creating the account
Domains - number of domains created within the account
To define the client account to which the selected domains should be migrated:
1 click an appropriate client account name in the list, or select the radio button next to
an appropriate client account,
2 click Next>> to proceed to to the IP mapping configuration.
52 Performing Migration
Setting up IP Mapping
On this step, you should configure IP mapping settings for the migration, that is, you
have to choose which Plesk IP addresses must be used for the remote host domains
when the migration is completed. This is a final step of Migration Manager wizard: once
you click Next>> on this page, transferring the data will start.
Figure 16: Migration Manager wizard: IP mapping step
This Migration Manager page shows the list of all remote host IP addresses assigned
to domains that were selected for the migration. Columns in the list provide the
following information:
T (type) - indicates the IP address type:
- exclusive IP address (can be assigned only to one client)
- shared IP address (can be assigned to many clients)
Source IP Address - IP assigned to an object in the source hosting platform
Destination IP - each line is a list of IP addresses registered in Plesk. The IPs that
are not assigned to any Plesk client are listed under Vacant IP Addresses. This list
contains all IP addresses from IP Pool of the target Plesk client account, all shared
IP addresses registered in Plesk and vacant exclusive IP addresses.
Before you perform IP mapping, it is important to keep the following in mind:
When you perform domains migration, both shared and exclusive source IPs can
be mapped to either shared or exclusive destination IPs.
Performing Migration 53
Several source IPs belonging to Ensim Pro IP-based sites can be mapped to one
exclusive IP address in Plesk. It is advised to use this capability with caution,
though, as allocating several migrated domains on one exclusive Plesk IP can
cause problems with some of the domain settings such as Anonymous FTP.
To perform mapping:
1 For each Source IP Address in the list, select Destination IP from the corresponding list
in the Destination IP column.
2 Click Next>>. This starts transferring data to Plesk.
If there are no enough destination IPs, you can register new IP addresses in Plesk
as follows:
1 Click IP addresses located in the Tools group. Doing this takes you to the IP
Addresses management page.
2 To register new IP, click Add New IP Address. Adding IP address page opens.
On that page, enter the data necessary for creating IP address in Plesk and click
OK.
When you have finished with adding IP addresses to Plesk, click OK or Up Level on the
IP addresses management page. Doing this takes you back to the Migration Manager
page of setting up IP mapping.
You also can access the IP pool of the client whose account is target for this migration:
Click IP Pool located in the Tools group. Doing this takes you to the IP Addresses
management page. When you are finished with adding new IP addresses or editing the
IPs existing in the pool, click OK or Up Level on the IP pool management page. Doing
this takes you back to the Migration Manager page of setting up IP mapping.
54 Performing Migration
Setting Up the Migration Preferences
On this step of the migration wizard you can:
View general information on the specified source host.
Set up the migration preferences.
Plesk Migration Manager has established connection to Plesk Migration Agent installed
on the specified remote server, and returned the data required for starting migration:
Figure 17: Plesk Migration Manager wizard: setting up migration preferences
Understanding Source Host Info
Source hosting platform - hosting platforms supported by Plesk Migration Agent that
were detected on the remote host.
„Hosting platform‟ here means the way that data related to hosting is organized. If
there is HELM installed on the remote server, you always see 2 hosting platforms
(Resellers and Users), which conceive two ways of migrating data (mapping HELM
Reseller accounts to Plesk Client accounts or HELM User accounts to Plesk Client
accounts). If Ensim Pro is installed on the remote server, only one hosting platform
(Ensim) is displayed.
Average CPU load - average CPU usage on the remote host.
When the source hosting platform is Unix, Average CPU load field will show you three
numbers, displaying average CPU load during the last 1, 5 and 15 minutes
respectively. If this value is too high, the migration can take longer. If this value is
too high, the migration can take longer.
Operating system - the detailed info on the operating system installed on the remote
server.
Specifying the Migration Preferences
Performing Migration 55
1 To define the data you wish to migrate, select an appropriate option under Migration
In this section:
Migrating Domains ............................................................................................ 56
Migrating User Accounts ................................................................................... 57
type:
To migrate all user accounts, domains, and objects that can be mapped to Plesk
domain and client templates (for example, if migrating data from HELM, these
objects are Reseller‟s and Hosting Plans), select Full migration.
To choose which objects to migrate, select Selective migration.
2 Select source hosting platform that must be used during the migration if there are
several platforms on the source server.
3 Click Next>>.
Selecting Objects For Migration
Depending on the migration preferences set up on the previous step, migration
manager returns the list of objects existing in the source hosting platform.
On this step, you should select which type of objects you want to migrate.
To define the type of objects you wish to migrate, switch to an appropriate migration
option by selecting Domains or Accounts tab:
Domains - migrating only data of the selected remote server domains to a Plesk
client account (which account it should be is defined on the next step).
Accounts - migrating selected user accounts data (including all domains registered
within those accounts).
Note: You cannot migrate both domains and accounts at the same time.
56 Performing Migration
Migrating Domains
The Domains tab opens the following page:
Figure 18: Plesk Migration Manager wizard: migrating domains
This page shows the list of all domains existing on the source server. Columns in the
list provide the following information:
S (status) - indicates domain‟s status in the scope of comparison to the list of
domains existing on Plesk server:
- domain with such name does not exist in Plesk, and is available for
migration
- domain with such name exists in Plesk: it cannot be migrated
Name - domain name
Login - login name of the user‟s account
To define the domains you want to migrate:
1 Select check boxes next to the domains you want to migrate.
To migrate all domains, select the upper check box.
2 Click Next>> to continue the migration with selected options.
Performing Migration 57
Migrating User Accounts
The Accounts tab opens the following page:
Figure 19: Migration Manager wizard: selecting user accounts for migration
This page shows the list of all domains existing on the source server. Columns in the
list provide the following information:
S (status) - indicates account‟s status in the scope of comparison to the list of
accounts existing on Plesk server:
- user account with such login does not exist in Plesk: it can be migrated to
Plesk, including all domains registered within this account in the source hosting
platform
- some names of the domains registered within this account match the
domain names existing in Plesk: the account itself and the rest of its domains
can be migrated to Plesk
- all names of the domains registered within this account match the domain
names existing in Plesk: only the account data can be migrated to Plesk
- user account with such login exists in Plesk: it cannot be migrated to Plesk
Login - login of the user‟s account
Client’s Name - real name of the account user
Number of domains - number of domains registered within this account in the source
hosting platform
To define the accounts you want to migrate:
1 Select check boxes next to the accounts you want to migrate.
58 Performing Migration
To migrate all accounts, select the upper check box.
2 Click Next>> to continue the migration with selected options.
Performing Migration 59
Selecting Target Client Account
The step of selecting target client account appears when migrating domains. On this
step, you should define the Plesk client account to which you wish to migrate the
selected domains, that is, you should choose the account of the client who will be the
owner of the migrated domains.
This page shows the list of all client accounts existing in Plesk. Columns in the list
provide the following information:
P (problem) - indicates the state of client‟s domain(s):
- resource usage of client‟s domains is within the defined limits
- disk space and/or traffic limitations are exceeded at the client‟s domains
S (status) - indicates the client account status in the system:
- account is active
- account is disabled
Client name - real name of the client
Company name - name of the company specified in client‟s personal information
Creation date - date of creating the account
Domains - number of domains created within the account
To define the client account to which the selected domains should be migrated, click an
appropriate client account name in the list or select the option button next to an
appropriate client account, and then click Next>> to proceed.
60 Performing Migration
Setting up IP Mapping
Setting up IP mapping is the last step of Migration Manager wizard. On this step, you
should configure IP mapping settings for the migration, that is, you have to choose
which Plesk IP addresses must be used for the remote host objects when the migration
is completed.
This Migration Manager page shows the list of all remote host IP addresses assigned
to objects that were selected for the migration. Columns in the list provide the following
information:
T (type) - indicates the IP address type:
- exclusive IP address (can be assigned only to one client)
- shared IP address (can be assigned to many clients)
Source IP Address - IP assigned to an object in the source hosting platform
Destination IP - each line is a list of IP addresses registered in Plesk. The IPs that
are not assigned to any Plesk client are listed under Vacant IP Addresses.
To perform mapping:
1 For each remote host IP address in the list, select Plesk IP from the corresponding
list in the Destination IP column.
2 Click Next>>. This starts transferring data to Plesk.
Note that Plesk IP addresses list appearing here depends on type of objects you
migrate:
full migration and accounts migration - there are all shared IP addresses registered
in Plesk and vacant exclusive IP addresses.
Note that in this case, remote host IPs of a shared type can be mapped only to
Plesk shared IPs.
domains migration - there are all IP addresses contained in IP Pool of the target
Plesk client account, all shared IP addresses registered in Plesk and vacant
exclusive IP addresses.
Note that in this case, remote host shared IPs can be mapped to Plesk either
shared or exclusive IPs.
If there are no enough destination IPs, you can register new IP addresses in Plesk as
follows:
1 Click IP addresses located in the Tools group. Doing this takes you to the IP
Addresses management page.
Performing Migration 61
2 To register new IP, click Add New IP Address. Adding IP address page opens.
On that page, enter the data necessary for creating IP address in Plesk and click
OK.
3 When you are with adding IP addresses to Plesk, click OK or Up Level on the IP
Addresses management page. This takes you back to the Migration Manager page
of setting up IP mapping.
To manage IPs assigned to the target client account, click IP Pool located in the
Tools group. Doing this takes you to the client‟s IP pool management page where you
can assign new IP addresses to the client and change properties of the IPs already
assigned to the client.
Finishing Migration
When a migration is completed, the final page of the Migration Manager wizard
appears, showing you the results of transferring hosting data from the source server to
Plesk.
If the migration passed successfully, you see the following page:
Figure 20: Migration Manager wizard: all the migration stages passed successfully
Click Finish to complete this migration.
If some stages of the migration failed, you see the migration details in the form of tree
where each branch represents a migration stage:
62 Performing Migration
Figure 21: Migration Manager wizard: some of the migration stages failed
The icon indicates that stage passed successfully.
The icon indicates that stage failed.
In this case, a message is shown saying what went wrong on the migration stage.
On the figure above, the problem occurred with migration of databases content; in
fact, the problem was caused by the lack of this content.
For the detailed information on the performed migration process, refer to the migration
log (see page 66).
This chapter presents the information on the most important post-migration matters and
In this chapter:
Informing Customers of Migration Results ......................................................... 64
Restoring File and Directory Attributes After the Migration ................................ 66
Viewing Migration Log ....................................................................................... 66
C H A P T E R 5
Post-Migration Issues
actions.
Once content has been migrated to Plesk, you can begin configuring the content in
Plesk the way you would normally do with the native Plesk content.
64 Post-Migration Issues
Informing Customers of Migration Results
After migrating to Plesk, your customers who had accounts and domains on the source
host should get to know about the migration and its results (contained in the migration
log (see page 66) file): what has been migrated, what new passwords and usernames
are, and so on.
To let you inform your customers easily, there is the ParseMigrLog.vbs script
located in the %plesk_dir%\PMM\ folder. This script divides the general migration log
file into a number of client migration log files (that is, each resulting file contains the
information concerning migration of a single Plesk client), and sends these files to the
clients e-mail addresses specified in their personal information.
Note: It is very important that you do not send the whole migration log to your clients.
Doing so disturbs customers privacy and security.
To make the script perform the described operations, do the following:
1 Copy the required migration log file
(%plesk_dir%\PMM\logs\AdminMigration.log) to the folder where the script
is located: %plesk_dir%\PMM\.
2 Open command prompt in a folder where the script is located as follows: press Start
> Run..., then execute the cmd /K “cd %plesk_dir%\PMM\” command.
3 Run the script entering the command string with appropriate options values.
Here is an example of the command string:
CScript ParseMigrLog.vbs /from:”admin@somehosting.com”
/code:”windows-1250” /srv:”127.0.0.1” /port:”25”
/name:”admin” /psw:”mypassword”
The following command options are available:
/from:”admin@somehosting.com” - defines the e-mail address that will be
in the message “From:” field (for example, “admin@somehosting.com”)
/srv:”127.0.0.1” - defines the name (for example, “smtp.mail.com”) or IP
address (for example, “127.0.0.1”) of a mail server that will be used for sending
e-mails to customers
/port:”25” - defines the mail server port number
/code:”windows-1250” - defines the code page for the e-mail message
/name:”name” - defines your e-mail account login
/psw:”password” - defines your e-mail account password
If, for some reason, the script fails to send client migration log files to clients by e-mail,
then it will create a folder \MigrUsersLogs\ and save the files to it. This folder will be
created in the same folder where the script is located. You can then send this files to
customers in some other way or change the script options and retry using the script.
Post-Migration Issues 65
You can also customize other script options by editing the script in a text editor, for
example, you can define the text for a subject of e-mail messages that are going to be
sent to clients or the text, from which the messages will begin. The script strings that
can be edited with no risk of the script corruption are followed by comments clarifying
the meaning of the string. The comment strings are preceded by apostrophe. For
example:
„ Migr Log Parser settings
Dim DoSendMail
DoSendMail = 0 „ 0 - divide migration log per
client into separate log files ..//MigrLogFolder
„ 1 -look for client‟s e-mail
addresses and try to send migration information using e-mail
Here you can change the default value of the DoSendMail variable setting it to “0”,
meaning that you do not want the script sending e-mail messages.
Warning: We strongly recommend you to create a backup copy of the script before
editing it, as it is not possible to restore it by Migration Manager means if you corrupt it.
You should also be very careful when editing and clearly realize what you are doing.
66 Post-Migration Issues
Restoring File and Directory Attributes
After the Migration
For the purpose of performing migration correctly, Migration Manager resets the “Read
Only” attribute from all migrated files and directories. Restoring the “Read Only”
attribute can be done manually after the migration is complete. This issue concerns the
migration from all supported platforms.
Viewing Migration Log
The migration process is logged: the information on the migration process is saved in
one file. The migration logs are located in the %plesk_dir%\PMM\logs\ folder
(where %plesk_dir% is the system variable defining the folder where Plesk is
installed).
Two types of log files are created during each migration process:
Migration.log - contains the most detailed information on all migration stages
and steps, including messages about errors that happened during the migration.
Note: We recommend you to refer to this log file if serious problems occur and if you
need the most detailed information on the migration.
Note that this log file is overwritten for every migration, so there is always only one
Migration.log file, which is associated with the migration that was most
recently performed.
AdminMigration.log - contains information on the most important steps of the
migration process. The main point about the AdminMigration.log file is that it
provides information on logins and passwords registered in Plesk after the
migration. This is important because some user‟s logins and passwords are
changed during the migration, and this log file is the only place where information
on these changes is present.
AdminMigration.log is created for each migration without overwriting. This is
achieved by adding to the file name numbers that indicate when the migration was
performed in the following format: AdminMigration_2005_11_18_10.log. The
name of log file in this example says that the migration was performed at 10:XX AM
on November 18, 2005. If you perform several migrations in one hour, numbers in
brackets will be added to the file name. For example, if you perform 3 migrations
from 10 AM to 11 AM, say at 10:15, 10:30 and 10:45, and it was the most recent
migration that you performed at 10:45, then 3 log files are created:
AdminMigration_2005_11_18_10[0].log,
AdminMigration_2005_11_18_10[1].log and
AdminMigration_2005_11_18_10.log.
Post-Migration Issues 67
AdminMigration.log file starts with the information on the source host (IP address
or server name) and type of the migration (full or selective), followed by the information
about the migrated objects. Log parts describing migration of each user account are
separated with strings containing equal marks (===). Log parts describing migration of
each domain are separated with strings containing hyphens (---).
Here is a sample part of log file created during the selective migration when accounts
are chosen as migration objects. It contains all types of strings that can be found in the
AdminMigration.log file:
11/18/2005 10:51:00 : Migration started from host: 10.0.0.1
11/18/2005 10:51:59 : Start selective migration
11/18/2005 10:52:13 : Processing Client RESELLER1 ...
11/18/2005 10:52:13 : Added UserName = Mary Smith, login = RESELLER1, password
= mxwur2
11/18/2005 10:52:13 : Added client e-mail = reseller1@sample_mail.com
11/18/2005 10:52:14 : Processing domain...
11/18/2005 10:52:14 : Added Domain name = domain1.com, display name =
domain1.com
11/18/2005 10:52:14 : Added Domain user = Chu Khon, login = domain1.com,
password = 4ev45k
11/18/2005 10:52:14 : Processing Hosting for domain domain1.com
11/18/2005 10:52:16 : Added Protected directory Hidden
11/18/2005 10:52:20 : Added Protected directory user = Chosen password = dkelv75ff
11/18/2005 10:52:43 : Added Shared SSL link domain2-com
11/18/2005 10:52:43 : Hosting added. domainName = domain1.com, ip = 10.57.102.1,
FTP login = domain1, password = 202321500
11/18/2005 10:52:45 : Added Domain alias domain-1.com
11/18/2005 10:52:45 : Added Domain alias domain-one.com
11/18/2005 10:52:47 : Set Mail to nonexistent user = Catch to address noones-
mail@domain1.com
11/18/2005 10:52:47 : Added Mail name= mailbox1, password = 4ev45k
11/18/2005 10:52:47 : Added Mail name= july2004, password = 29fj0wnf
11/18/2005 10:53:03 : Processing Database... DBName = Gallery1
11/18/2005 10:53:03 : Processing Database users...
68 Post-Migration Issues
11/18/2005 10:53:03 : Added Database user, login = gallery1_a, password =
xmwyd3hd
11/18/2005 10:53:03 : Added Database user, login = gallery1_b, password = l2lcllld8s
11/18/2005 10:53:03 : Success. Microsoft SQL database Gallery1 configuration added
11/18/2005 10:53:03 : Processing Database... DBName = PA_kkejd235kdmmrk
11/18/2005 10:53:03 : Processing Database users...
11/18/2005 10:53:03 : Changed Database user name for MySQL database
PA_kkejd235kdmmrk. Original name = „cshjtrby37dsjlbe003452‟, New name =
„cshjtrby37dsjlbe‟
11/18/2005 10:53:03 : Success. MySQL database PA_kkejd235kdmmrk configuration
added
11/18/2005 10:53:03 : Added ODBC DSN SQLserverDSN
11/18/2005 10:53:03 : Added ODBC DSN Access
11/18/2005 10:53:03 : Domain domain1.com migrated successfully
11/18/2005 10:53:03 : -------------------------------------------------11/18/2005 10:53:23 : Success. Microsoft SQL database Gallery1 content added
11/18/2005 10:53:23 : Success. MySql database PA_kkejd235kdmmrk content added
11/18/2005 10:53:23 : Client Mary Smith migrated successfully
11/18/2005 10:53:23 :
==================================================
The information presented in this chapter can help you solve problems that may appear
In this chapter:
Complying with Plesk Limits .............................................................................. 69
User Databases Migration ................................................................................. 70
Solving Problems With Accessing Domain Contents Through Shared SSL ....... 76
Solving Problems With ODBC DSN Migration ................................................... 77
Solving Problems With Accessing Web Users Content ..................................... 78
Solving Problems With Web Applications .......................................................... 78
Solving Problems With Virtual Directories Content ............................................ 79
Solving Problems with Connectivity Between PMM Components ...................... 79
Solving Problems With Migration of Domains, Subdomains, and Domain Aliases 80
Plesk Parameter
Migration Type
Migration Outcome if Parameter Exceeded
Licence Key Maximum Number
of Client Accounts
Full, Client
Only the number of client accounts allowed for a
given Plesk installation will be migrated. The
rest of client accounts will not be migrated.
Licence Key parameters:
Maximum Number of
Domains
Maximum Number of Mail
Accounts
Maximum Number of Web
Users
Full, Partial, Client,
Domain
Only the number of domains allowed for a given
Plesk account will be migrated to the account,
the rest of the domains on the legacy platform
account will not be migrated.
C H A P T E R 6
Troubleshooting
with migrations when using Plesk Migration Manager.
Note: In the unlikely event that you experience a problem that is not described in this
section, you can find a quick solution at the Parallels (formerly SWsoft) customer
support forum: http://forum.parallels.com.
Complying with Plesk Limits
If during migration domain or account limits set on the legacy platform come into
conflict with the limits set in Plesk, such domains or accounts will not be migrated.
The following table illustrates Plesk parameters that cannot be exceeded.
70 Troubleshooting
Plesk client account limits: disk
space quota limit
Domain
During domain migration, if disk space limit set
on a domain on a legacy platform exceeds disk
space limit set for the client account to which
the domain is migrated, the domain will not be
migrated.
To avoid this problem, set the Plesk account
disk space limit to “unlimited” temporarily during
migration.
In this section:
Solving Problems With Site Applications Which Use Migrated Databases ......... 71
Solving Problems With Migrating Databases to Plesk ....................................... 72
Database Migration to Plesk 8.1.1 and Later Versions ...................................... 75
User Databases Migration
This section provides information necessary for solving problems that may appear with
migrating user databases. It answers the following questions:
1 Why site application using database that was successfully migrated does not work
and how can I solve it?
(Refer to the Solving Problems With Site Applications Which Use Migrated
Databases (on page 71) section.)
2 Why user database or its content was not migrated and what can I do to migrate it
to Plesk?
(Refer to the Solving Problems With Migrating Databases to Plesk (on page 72)
section.)
3 What is new in the database hosting in Plesk 8.1.1 and later versions, how
databases are migrated to these versions of Plesk, and the database migration
process is affected.
(Refer to the “Databases Migration to Plesk 8.1.1. and Later Versions” section.)
Troubleshooting 71
Solving Problems With Site Applications Which Use
Migrated Databases
If a domain has been migrated to Plesk and its applications that use databases do not
work, there can be three reasons:
User database configuration and content have not been migrated.
One or more databases have been renamed during migration because databases
with such names already exist in Plesk, or database names exceeded the Plesk
database name length limit (depends on the Plesk version) and have been
truncated.
Database has been migrated, but logins for database users were changed during
the migration. This happens if database user login existing in source hosting
platform contains more than the maximum length supported by Plesk (depends on
the Plesk version).
To solve your problem with site applications, do the following:
1 Verify that migrated databases have not been renamed:
1. Open the AdminMigration.log (see page 66) file.
2. Check if there are log messages about these databases saying
The name of the <db_type> database <db_name> on domain
<domain_name> was shortened because it is longer than the
maximum database name length allowed in Plesk. The new name
is <new_db_name>
(In real error messages, <db_name> is the name of the database on the source
server; <db_type>is the database server (Microsoft SQL Server or MySQL);
<domain_name> is the name of the domain to which the database belongs to,
<new_db_name> the new database name in Plesk that will be used in the log
from this point on to refer to the database.)
2 Verify that the database used on the domain has been successfully migrated to
Plesk:
1. Open the AdminMigration.log (see page 66) file.
2. Check if there are log messages about this database saying
Success. <db_type> database <db_name> configuration added
Success. <db_type> database <db_name> content added
(In real error messages, <db_name> is replaced with the name of the database,
<db_type> database server (Microsoft SQL Server or MySQL).)
If there is no such message for the problem database in the log, then problems
were encountered during the database migration. For information on the solutions,
refer to the Solving Problems With Migrating Databases to Plesk (on page 72)
section.
3 Find in the AdminMigration.log file strings of such format:
Changed database user name for <db_type> database <db_name>.
Original name = „<original_name>‟, New name = „<new_name>‟
72 Troubleshooting
(In real error messages, <db_name> is replaced with the name of the database,
Error Message
Problem Description
Troubleshooting
method
Migration Details:
“Migrating content of <db_type>
database <db_name> skipped”
The database configuration was
migrated to Plesk, but its content
was not.
Occurs when Migration Manager
cannot find the database dump
due to one of the following
reasons.
Migration Agent could not
connect to database server
There is no disk space on
either source server or Plesk
server
Connection to remote
Microsoft SQL server is
configured on the source
server
1. Create the
database dump
(see Procedure 5).
2. Then restore the
dump (see
Procedure 2).
AdminMigration.log:
Backup file for <db_type>
database <db_name> not
found
<db_type> with database server (Microsoft SQL Server or MySQL),
<original_name>, with database user login existed in the source hosting panel,
<new_name>, with the login created for this database user in Plesk.)
4 In the scripts used by the application for connecting to the database, replace the old
database names if necessary. Also, replace old logins of database users with new
ones.
Solving Problems With Migrating Databases to Plesk
To solve your problem with a user database migration:
1 Basing on the error message shown in migration details on the Migration
Completed page (see page 61), find the error message about the database in the
AdminMigration.log (see page 66) file.
2 Find these error messages in the Error Message column in the table below and
determine your problem and the way of its solving by viewing corresponding lines in
the Problem Description and Troubleshooting Method columns.
3 Follow steps from the Troubleshooting Method column.
Each step is one of the troubleshooting procedures listed below this table.
Note: During the migration from Plesk For Unix, PostgreSQL databases are not
transferred, since Plesk for Windows doesn‟t support PostgreSQL. If PostgreSQL
databases were encountered during the migration process, the error saying
“Unsupported database type postgresql” will be displayed on the Migration Results
page.
Determining Problem
Troubleshooting 73
Migration Details:
“<db_type> database <db_name>
skipped”
Neither configuration nor content
of the database was migrated to
Plesk.
Migration Manager could not
restore database dump on Plesk
server because no database
server of a defined type is
configured in Plesk.
1. Get the database
dump (see
Procedure 1).
2. Restore it (see
procedure 3).
AdminMigration.log:
<db_type> server is not
configured. Migration of
the database <db_name>
skipped
Migration Details:
“<db_type> database <db_name>
skipped”
Neither configuration nor content
of the database was migrated to
Plesk.
Migration Manager could not
restore database dump on Plesk
server because the server does
not have database server
service running or Plesk has
incorrect database server
configuration.
1. Get the database
dump (see
Procedure 1).
2. Restore it (see
Procedure 3).
AdminMigration.log:
Connection to <db_type>
server cannot be
established. Migration of
the database <db_name>
skipped
Migration Details:
“Migrating content of Microsoft
SQL database <db_name>
skipped”
The database configuration was
migrated to Plesk, but its content
was not.
Migration Manager could not
restore the database dump on
remote Microsoft SQL server
configured in Plesk.
1. Get the database
dump (see
Procedure 1).
2. Restore it (see
Procedure 4).
AdminMigration.log:
Unable to restore the
content of Microsoft SQL
database <db_name>. Plesk
does not support
restoring Microsoft SQL
databases on remote
server. Only the database
configuration will be
restored in Plesk.
Migration Details:
“<db_type> database <db_name>
skipped”
Neither configuration nor content
of the database was migrated to
Plesk.
Migration Manager failed to
restore the database dump,
because database with such
name already exists on Plesk
server.
1. Get the database
dump (see
Procedure 1).
2. Restore the
dump with a new
name (see
Procedure 3).
AdminMigration.log:
Cannot restore <db_type>
database <db_name>.
Database with such name
already exists in Plesk
74 Troubleshooting
Note: <db_name> in real error messages is replaced with the name of the database,
<db_type> database server (Microsoft SQL Server, PostgreSQL or MySQL).
Troubleshooting Procedures
1. Getting database dump
The way of getting database dump depends on whether the dump is present in
Plesk or not. To find it out, search for the <db_name>.<db_type>.tgz file on
Plesk server (<db_type> can be either “mssql” or “mysql”). By default,
database dumps are stored in
%plesk_dir%\PMM\Store\Main\PleskDump\databases folder. If the
dump folder name and/or location were changed by editing the Migration
Manager configuration file (see page 31), refer to it to find out the dump
location.
Database dump was found on the Plesk server.
Unpack the <db_name>.<db_type>.tgz file. Regular ZIP archivers usually allow
unpacking .tgz archives.
Database dump was not found on the Plesk server.
You have to make the database dump yourself (see Procedure 5).
2. Restoring database content (configuration migrated to Plesk)
1 Restore the database from the dump (see Procedure 5).
2 In database server, create the corresponding database user with their permissions
using Plesk database configuration as a reference.
MySQL database - for each database user configured for this database in Plesk,
create MySQL user with the necessary permissions for the restored database.
Microsoft SQL Server database - for each database user configured for this
database in Plesk, create Microsoft SQL Server logins with the necessary
permissions for the restored database.
3. Restoring database configuration and content
1 In Plesk, create the database of the necessary type having the necessary name.
2 In Plesk, create the database users, the way they were at the source host.
Now a configured database without actual content exists in Plesk.
3 Restore the migrated database dump into this “empty” database (see Procedure 5).
Note: When restoring Microsoft SQL database, please remember to specify the
REPLACE option. Also, restore the connection between users and logins.
4. Restoring Microsoft SQL database on remote Microsoft SQL Server
configured in Plesk
The same remote database server is configured in both source hosting panel and
The way or restoring Microsoft SQL database on remote database server depends
on whether the same database server is used by both source hosting panel and
Plesk or the different servers are used.
Plesk
Troubleshooting 75
1. There is no need in dumping and restoring database, as it already exists on the
database server.
2. Verify that all database users configured in Plesk exist on the database server
and, if not, create the missing users on the database server with regard to the
database users‟ data in Plesk.
This is necessary because logins of database users are modified during
migration process if they contain more than 16 characters (the maximum length
of database user login supported by Plesk). To find out which database users‟
logins were modified by the Migration Manager, refer to the
AdminMigration.log (on page 66) file.
Different database servers are used in source hosting panel and Plesk
Restore database content as described in Procedure 2.
5. Creating/restoring dumps on database servers
To create/restore dumps on MySQL server, use the mysqldump and mysql utilities
included in MySQL server installation.
For detailed information and instructions, refer to the MySQL information resources
located at http://www.mysql.com/.
To create/restore dumps on Microsoft SQL Server, use Microsoft SQL Server
Enterprise Manager.
Or, execute the commands BACKUP DATABASE and RESTORE DATABASE using
any program which allows SQL queries execution. (For example, Query Analyzer or
osql.exe utility.)
Note: While backing up Microsoft SQL database, database dump is saved on the
machine where Microsoft SQL Server is installed. This is also important for restoring:
database dump must be located on the machine where the target for restoring
Microsoft SQL Server is installed.
For detailed information and instructions, refer to the Microsoft documentation
http://www.microsoft.com/sql.
Database Migration to Plesk 8.1.1 and Later Versions
Both local and remote database servers can be used to host databases of the same
type in Plesk 8.1.1 and later versions. During databases migration, PMM picks a single
target Plesk database server for migration of databases of the same type according to
the following rules:
1 If the Plesk default database server is installed on the local Plesk server, databases
are migrated to the default database server.
2 If the Plesk default database server is located on a remote machine, then
databases are migrated to one of the local database servers.
3 If no local database server is found, then databases are migrated to the remote
Plesk default database server.
76 Troubleshooting
Consult the AdminMigration.log file (on page 66) for information about the database
server to which databases are migrated. Look for phrases like this: “User database
db_example on domain example.com will be migrated to Microsoft
SQL database server 127.0.0.1\SQLEXPRESS”.
Solving Problems With Accessing Domain
Contents Through Shared SSL
If a domain migrated from Ensim Pro used Shared SSL, its secure content will not be
accessible after the migration. The reason of this problem is that due to the feature
implementation differences, all secure Ensim Pro content is mapped to non-secure
Plesk content. Secure Plesk domain content is located in a domain‟s httpsdocs
folder. If you want to restore secure access to content, you need to manually relocate
the required folders from a domain‟s httpdocs folder to a domain‟s httpsdocs folder
after the migration is completed.
You can use Plesk File Manager to perform content relocation. To access the File
Manager, follow these steps:
1 Click Domains in the navigation pane.
2 Click the required domain name in the list.
3 Click File Manager in the Hosting section of the work pane.
To learn how to use Plesk File Manager, refer to Plesk for Windows Administrator’s
Guide corresponding to your version that is available at the Parallels (formerly SWsoft)
web site http://www.parallels.com/en/download/plesk/products/.
Note: Moving the folders and their content is the best relocation method we
recommend, as opposed to copying.
To find out what folders need to be relocated in order to make the content secure, refer
to the post-migration content location table, which can be found in Domains Mapping
(see page 148) section.
After the relocation is complete, your content will be securely available through the
previously used URL, that is, „https://masterssldomain.com/yourdomain.net‟ where
„masterssldomain.com‟ is a domain that shares its SSL certificate with your domain,
and „yourdomain.net‟ is your domain that uses shared SSL certificate.
Note: If you relocate content back from httpsdocs folder, security settings might be
lost (depending on how relocation was carried out) and Web access to domain content
can be compromised. If this happens, run Plesk Reconfigurator, choose Repair Plesk
Installation mode and select Plesk Virtual Host Security to repair security settings and
restore Web access to domain content.
Also note that it is strongly recommended to check all Web application scripts intended
for working in secure environment to possibly avoid problems described above.
Troubleshooting 77
Solving Problems With ODBC DSN
Migration
ODBC DSN will not work after the migration from Ensim Pro. The solution to this
problem depends on the DSN connection type.
To repair Microsoft SQL Server DSN connection, you need to manually specify login
and password for it:
1 Click Server in the navigation pane.
2 Click ODBC Settings in the Services section of the work pane.
3 Click the required ODBC connection name in the Connection name column.
4 Enter the login in the [UID] Login ID field.
5 Enter the password in the [PWD] Password field.
6 Click Test to check whether the connection will work with supplied credentials.
7 Click Finish if test was successful, otherwise check if all supplied data is correct.
If Microsoft Access DSN connection is not configured after the migration, you need to
check whether the database file was migrated to Plesk. If the file wasn‟t migrated (this
can happen if it was located in one of the Ensim Pro folders ignored during the
migration), you need to do the following in order to repair Microsoft Access DSN
connection:
1 Manually copy the database file to one of the domain folders of your choice in
Plesk.
2 Click Server in the navigation pane.
3 Click ODBC Settings in the Services section of the work pane.
4 Click the required ODBC connection name in the Connection name column.
5 Input the path to the manually copied file in the [DBQ] Database File Path input field.
6 Click Next>> to automatically configure the connection.
7 Click Finish if test was successful, otherwise check if all DSN connection data is
correct.
78 Troubleshooting
Solving Problems With Accessing Web
Plesk For Windows
Plesk For Unix
cgi
cgi-bin
html
httpdocs
shtml
httpsdocs
private
private
Users Content
The content belonging to Web users will not be accessible through the previously used
Web addresses after the migration from Ensim Pro. The reason is that Plesk uses
addresses like „http://domain.com/~webuser‟ to access Web user content, while Ensim
Pro uses different addresses (like „http://domain.com/webuser‟) for the same task.
To access Web user content after the migration, simply add the tilde sign (~) before the
Web user name in the address: „http://domain.com/~webuser‟.
Solving Problems With Web Applications
After the migration from Ensim Pro, cPanel v. 9 and 10, or Plesk for Linux/Unix, some
Web applications might not work, displaying the error message regarding the inability
to find the required folders and files. The actual message text varies and depends on
the application. This problem is caused by directory structure changes during the
migration. To solve this problem, go to Web application settings and change old, nonworking path to new, correct one.
To learn the new path to the required folders and files after the migration from Ensim
Pro, refer to Web Site Content (see page 149) section for the detailed information
regarding the location of post-migration Web site content.
To learn the new path to the required folders and files after the migration from Plesk for
Linux/Unix, see the table below:
Application Data Paths
Troubleshooting 79
Solving Problems With Virtual Directories
Content
Sometimes, external links to a domain‟s particular virtual directory are broken after the
migration from Ensim Pro. This problem is caused by directory structure changes
during the migration.
To solve this problem, refer to Web Site Content (see page 149) section to learn more
about domain directory structure after the migration, and to determine whether the
required virtual directory was migrated or not.
If the virtual directory was created, simply change all required external links according
to the post-migration directory structure.
If the virtual directory was not migrated, do the following:
1 Create the required virtual directory in Plesk according to the domain directory
structure.
To create a virtual directory in Plesk, use Web Directories feature:
1. Click Domains in the navigation pane.
2. Click the required domain name in the list.
3. Click Web Directories in the Hosting section of the work pane.
4. Navigate through web directories structure and click Add New Virtual Directory.
To learn how to use Web Directories feature, refer to Plesk for Windows
Administrator’s Guide corresponding to your Plesk version that is available for
download at the Parallels (formerly SWsoft) web site
http://www.parallels.com/en/download/plesk/products/.
2 Manually transfer the data from Ensim Pro virtual directory to the virtual directory
you created in Plesk.
You can use Plesk File Manager to perform the data transfer. To access the File
Manager, follow these steps:
1. Click Domains in the navigation pane.
2. Click the required domain name in the list.
3. Click File Manager in the Hosting section of the work pane.
To learn how to use Plesk File Manager, refer to Plesk for Windows
Administrator’s Guide corresponding to your Plesk version.
Solving Problems with Connectivity
Between PMM Components
80 Troubleshooting
Certain machine or network configurations may cause connectivity problems between
Error message
Problem Description
Solution
PMM and Migration Agent. When this happens, PMM displays the following warning
message:
Network connection failed. Cannot connect to Plesk Migration Agent on the remote host
If you experience the problem, do the following*:
1 Stop migration.
2 Check the IP address key value in the Migration Agent configuration file (on page
34) WINAgentMng.exe.config.
If the key is not specified, or is set to 0.0.0.0, specify a valid IP address for
the key, and do the following:
1. Start PMM. On the Remote Host Connection Setup screen, type the IP address
specified in the IP address key in the WINAgentMng.exe.config file
into the Source host field under Remote host connection settings.
2. Proceed with migration as described in the “Performing Migration” (on page
39) section.
If a specific IP address is set for the IP address key in the
WINAgentMng.exe.config file, make sure that it is a valid address and that it
is the same as the address entered in Source host field on the Remote Host
Connection Setup screen during Migration setup (on page 39). If it is different,
either set the value of the key to “0.0.0.0” or remove the key from the
WINAgentMng.exe.config file altogether.
* - If Plesk Migration Manager is installed behind a NAT and you experience this
problem, it cannot be resolved in such a way. You should get both servers to connect
without the NAT between them and enable the migration.
Solving Problems With Migration of
Domains, Subdomains, and Domain
Aliases
A common reason why domains, subdomains, or domain aliases fail to migrate is
because their names coincide with names of other objects that already exist in Plesk or
in the migration dump. If an error of this type occurs, the AdminMigration.log file
will contain one of the error messages listed in the following table. Each message
indicates a failure of migration of a domain, a subdomain, or a subdomain alias.
Consult this table to determine migration problem by its error message and to find a
solution to remedy the problem.
Troubleshooting 81
Domain <domain name>* will
not be migrated because its
name coincides with the name
of domain alias <domain
alias>* for domain <domain
name> already present in the
migration dump.
A domain with the
name coinciding with
the domain alias is
already present in the
migration dump.**
Change the domain
name or the domain
alias on the remote
machine to resolve the
conflict and then repeat
migration.
Domain alias <domain alias>
for domain <domain name> will
not be restored because a
domain with the same name is
already present in the
migration dump.
A domain alias
coinciding with the
domain name is
already present in the
migration dump.**
Domain alias <domain alias>
for domain <domain name> will
not be migrated because a
subdomain with such name
already exists in Plesk.
A domain or a
subdomain with the
name coinciding with
the domain alias
already exists in
Plesk.
Change the name of the
domain aliascorresponding object***
on the remote machine
or the domain or
subdomain name in
Plesk to resolve the
conflict and then repeat
migration.
Domain alias <domain alias>
for domain <domain name> will
not be migrated because a
domain with such name already
exists in Plesk.
Domain <domain name> will not
be migrated because a domain
alias <domain alias> with
such name already exists in
Plesk on domain <domain
name>.
A domain alias
coinciding with the
domain name already
exists in Plesk.
Change the domain
name on the remote
machine or the domain
alias in Plesk to resolve
the conflict and then
repeat migration.
Subdomain <subdomain name>*
will not be migrated because
a domain alias with such name
already exists in Plesk on
domain <domain name>.
A domain alias
coinciding with the
subdomain name
already exists in
Plesk.
Change the subdomain
name on the remote
machine or the domain
alias in Plesk to resolve
the conflict and then
repeat migration.
While restoring, domain
<domain name> is skipped
because a domain or subdomain
with this name <domain name>
already exists in Plesk.
A domain or a
subdomain with the
same name already
exists in Plesk.
Change the domain
name on the remote
machine or the domain
or subdomain name in
Plesk to resolve the
conflict and then repeat
migration.
While restoring, subdomain
<subdomain name> of
domain<domain name> is
skipped because a domain or
subdomain with this name
<subdomain name> already
exists in Plesk.
Change the subdomain
name on the remote
machine or the domain
or subdomain name in
Plesk to resolve the
conflict and then repeat
migration.
82 Troubleshooting
* - In real error messages, <domain name> and <subdomain name> are replaced
with the name of the corresponding domain or subdomain, <domain alias> is
replaced with the corresponding domain alias.
** - When a domain alias-corresponding object and a domain on a remote machine are
in conflict, the domain alias is migrated instead of the domain only if the domain has
none of the following: physical hosting, domain forwarding, databases, mailboxes, and
mailing lists. Otherwise, the domain will be migrated instead of the domain alias.
*** - For migrated object transformation rules during migration from a particular
platform, consult the corresponding platform migration appendix.
Plesk parameter
Value
Origin/Conditions
Domain creation
Selected
default
C H A P T E R 7
Appendix 1. HELM Data Mapping
Reference
This chapter describes the way of migrating hosting data from server running HELM to
remote Plesk server. It answers the following questions:
1 What are the migration results? What data are transferred to Plesk after the
migration completion? Where do I find them in Plesk?
2 What is the origin of the data: were the parameters values set by default or were
they taken from Helm?
3 What is the exact Helm source for a Plesk parameter, and what is the principle of
its mapping?
The information in this chapter is grouped in sections in a way that you can see it in
Plesk user‟s interface. Each section begins from the instruction on how to find the data
in the control panel interface.
Note: We recommend that you first familiarize yourself with Plesk interface principles
stated in the Becoming Familiar with Plesk section of the Plesk Administrator‟s guide.
For information on meaning of Plesk parameters and objects refer to Plesk for
Windows Administrator’s Guide corresponding to your Plesk version that is available
for download from the Parallels (formerly SWsoft) web site
http://www.parallels.com/en/download/plesk/products/.
For convenience, the information in sections is presented in the form of tables like the
one below:
Permissions section
84 Appendix 1. HELM Data Mapping Reference
In this chapter:
Users Mapping .................................................................................................. 85
Templates Mapping ........................................................................................... 91
Domains Mapping ............................................................................................. 96
Each table corresponds to a certain Plesk page or to a section of options on a
page, whose name precedes the table (for example, “Permissions section”).
The Plesk parameter and the Value/Conditions columns represent the Plesk data as
they are after the migration (in the form they are displayed in Plesk user interface):
in the Plesk parameter column, parameter names are specified, while the Value
column presents exact values of this parameters. In the Value column you find the
following parameter values:
<specific value> - a fixed value that is set for a parameter in Plesk
Selected - check box corresponding to the parameter is selected
Selected if - check box corresponding to the parameter is selected on the
conditions defined in the third column
Cleared - check box corresponding to the parameter is not selected
Enabled - feature is enabled (in a way differing from selected check box)
Enabled if - feature is enabled on the conditions defined in the third column
Disabled - feature is disabled (in a way differing from cleared check box)
Equal to - value for a parameter is equal to the value of Helm notions defined in
the third column
other values specific for Plesk parameters
The Origin/Conditions column provides the information clearing up the contents of
the first two columns: either an exact source of a Plesk parameter value, or a
condition under which a parameter possesses the value. You can see there the
following:
name of an exact Helm object or parameter (in terms of Helm)
default - parameter value is not migrated from Helm, but defaults to what is set
by Migration Manager.
Appendix 1. HELM Data Mapping Reference 85
Users Mapping
In this section:
Client ................................................................................................................. 86
Domain Administrator ........................................................................................ 89
1. What types of user accounts exist in Plesk?
Plesk is operated at the four administration levels: administrator, client, domain
administrator, and e-mail user (listed from the highest to the lowest level). Each
higher administration level includes the functionality of the lower administration
levels, that is, they form a subordinate hierarchy of administration levels toward the
top “administrator” level.
All the levels correspond to the types of users that are each characterized by
specific set of settings: administrator, client, domain administrator, and e-mail user.
2. What is the principle of mapping Helm user data to the user accounts in
Plesk?
1 Mail user in Plesk is an owner of a mailbox corresponding to a Mail account.
He/she has an administrative access only to his/her mailbox on a domain. Since
Helm POP3 accounts are migrated to Plesk with the disabled Control Panel Access
option (refer to the Mail (on page 103) section of the current chapter), Plesk mail
users are not created during the migration.
2 As for Plesk Clients/Domain administrators data, it inherits Helm Reseller and User
accounts settings (along with the Plans they were created under and/or the Plans
they possess, and the packages they have). The result of migration depends on the
source hosting platform selected for the migration (“Helm (Reseller)” or “Helm
(User)”):
Plesk Client accounts inherit Reseller or User accounts settings
Plesk Domain administrator accounts inherit User accounts settings or are not
created
86 Appendix 1. HELM Data Mapping Reference
Client
Plesk parameter
Value
Origin/Conditions
Status
Reseller/User status was Active
Reseller/User status was Suspended,
Disabled or Pending approval
Client name
equal to
First Name(s) + Last Name*
Company name
equal to
Company Name
Creation date
equal to
the time of migrating to Plesk
Domains
equal to
number of domains migrated with this
account to Plesk
Plesk parameter
Value
Origin/Conditions
Company name
Equal to
Company Name
Contact name
Equal to
First Name(s) + Last Name*
Phone
Equal to
Daytime Tel. or Mobile Tel. or Evening
Tel.**
To access the list of Plesk Client accounts, click Clients in navigation pane. Columns in
the list provide the following information:
P (problem) - indicates the state of client‟s domain(s).
- Resource usage of client‟s domains is within the defined limits
- Disk space and/or traffic limitations are exceeded at the client‟s domains
S (status) - indicates the client account status in the system.
- Account is active
- Account is disabled
Client name - real name of the client
Company name - name of the company specified in client‟s personal information
Creation date - date of creating the account
Domains - number of domains created within the account
This information about each client is the following:
To access the settings page for a certain Client account, click a Client‟s name in the list
of Clients.
A Client personal information page opens when you click the Edit button located in
Tools section in work area. Client data after the migration are the following:
Personal Information
Appendix 1. HELM Data Mapping Reference 87
Fax
Equal to
Fax
E-mail
Equal to
Primary Email Address or Secondary Email
Address***
Address
Equal to
Address
City
Equal to
Town
State/Province
Equal to
State/County
Postal/Zip code
Equal to
Zip/PostCode
Country
Equal to
Country
Plesk parameter
Value
Origin/Conditions
Domain creation
Selected
default
Physical hosting management
Selected if
Web Resource enabled
Hard disk quota assignment
Selected
default
Subdomains management
Selected if
Web Resource enabled
Domain limits adjustment
Selected
default
DNS zone management
Selected if
DNS Resource and DNS Zone Editor
enabled*
* - Plesk Contact name represents the combination of the First Name and the Last Name
defined in Helm administrator‟s Personal Details.
** - As the Personal information in Plesk may contain only one telephone number, the
existing Helm telephone number with the highest priority is migrated. The priorities are
assigned to the numbers by the migration agent during the migration process: the first
priority is assigned to the Daytime Tel., the second one to the Mobile Tel., and the third
one to the Evening Tel.
*** - As the Personal information in Plesk may contain only one e-mail address, the
existing Helm e-mail address with the highest priority is migrated. The priorities are
assigned to the addresses by the migration agent during the migration process: the first
priority is assigned to the Primary E-mail Address, and the second one to the Secondary E-
mail Address.
Permissions And Limits
Permissions and limits for a Plesk Client account inherit the properties of a Reseller‟s
Plan, to which a Helm Reseller was subscribed (in the case of “Helm Reseller to Plesk
Client” migration), or the summarized properties of all Hosting Packages possessed by
a Helm User (in the case of “Helm User to Plesk Client” migration).
To access a Client Permissions/Limits page, click the Permissions or Limits buttons
located in the Tools section on a Client account page.
Permissions
Client permissions after the migration are the following:
88 Appendix 1. HELM Data Mapping Reference
Log rotation management
Selected
default
Scheduler management
Selected
default
Anonymous FTP management
Selected if
FTP Resource enabled
Web applications management
Cleared
default
System access management
Cleared
default
Mailing lists management
Selected if
Mail Resource enabled
Antivirus management
Selected
default
Backup/restore functions
Selected
default
Site Builder
Cleared
default
Plesk parameter
Value
Origin/Conditions
Maximum number of domains
Equal to
Domains
Maximum number of domain aliases
Equal to
Domain Aliases
Maximum number of subdomains
Equal to
Web Resources -> Sub Domains
Disk Space
Equal to
Disk space
MySQL database quota
Unlimited
default
Microsoft SQL database quota
Unlimited
default
Maximum amount of traffic
Equal to
Bandwidth
Maximum number of Web users
Unlimited
default
Maximum number of MySQL
databases
Equal to
Database Resources -> MySQL Databases
Maximum number of Microsoft SQL
Server databases
Equal to
Database Resources -> (MSSQL Server
2000 Databases + MSSQL Server 7
Databases)**
Maximum number of mailboxes
Equal to
Mail Resources -> POP3 Accounts
Mailbox quota
Unlimited
default
Maximum number of mail redirects
Equal to
Mail Resources -> Mail Aliases
Maximum number of mail groups
Equal to
Mail Resources -> Multi-Recipient
Addresses
Maximum number of mail
autoresponders
Unlimited
default
Maximum number of mailing lists
Unlimited
default
Maximum number of web applications
Unlimited
default
* - DNS zone management permission value is selected only if both DNS Resource and DNS
Zone Editor were enabled in the Helm Reseller/Hosting Plan.
Limits
Client limits after the migration are the following:
Appendix 1. HELM Data Mapping Reference 89
Maximum number of IIS application
pools
Unlimited
default
Maximum number of shared SSL links
Equal to
Web Resources ->Shared SSL
Validity period
Unlimited
default
Plesk parameter
Value
Origin/Conditions
Allow domain administrator‟s access
Selected
default
Display (...) lines per page
none
default
Button label length
none
default
Domain administrator‟s language
English
default
Domain administrator‟s interface skin
WinXP
Reloaded
Compact
default
Allow multiple sessions
Selected
default
** - Maximum number of Microsoft SQL Server databases limit value equals to the sum of
Helm values for MSSQL Server 2000 Databases and MSSQL Server 7 Databases.
Domain Administrator
The creation of Domain administrator accounts takes place if
Helm (Reseller) was selected as a source hosting platform for migration and
Accounts were selected as migration objects
or
Domains were selected as migration objects with no regard to the selected HELM
platform.
A Domain administrator account inherits the settings of a Helm User account, and is
created within a domain that belonged to this Helm User.
Note: Domain administrator‟s login is always equal to the user‟s domain name.
To access a page of a domain administrator account, follow these steps:
1 Click Domains in navigation pane.
2 Click a domain‟s name in the list of domains in work area.
3 Click the Domain User button located in Domain section.
The page of a Domain administrator account contains the following data:
Preferences section
90 Appendix 1. HELM Data Mapping Reference
Plesk parameter
Value
Origin/Conditions
Physical hosting management
Selected if
Web Resource enabled
Hard disk quota assignment
Selected
default
Subdomains management
Selected if
Web Resource enabled
DNS zone management
Selected if
DNS Resource and DNS Zone Editor
enabled*
Log rotation management
Selected
default
Scheduler management
Selected
default
Anonymous FTP management
Selected if
FTP Resource enabled
Web applications management
Cleared
default
System access management
Cleared
default
Mailing lists management
Selected if
Mail Resource enabled
Antivirus management
Selected
default
Backup/restore functions
Selected
default
Site Builder
Cleared
default
Plesk parameter
Value
Origin/Conditions
Company name
Equal to
Company Name
Contact name
Equal to
First Name(s) + Last Name*
Phone
Equal to
Daytime Tel. or Mobile Tel. or Evening
Tel.**
Fax
Equal to
Fax
E-mail
Equal to
Primary E-mail Address or Secondary Email Address***
Address
Equal to
Address
City
Equal to
Town
State/Province
Equal to
State/County
Postal/Zip code
Equal to
Zip/PostCode
Country
Equal to
Country
Permissions section
* - DNS zone management permission is selected only if both DNS Resource and DNS Zone
Editor were enabled in the Helm Reseller/Hosting Plan.
Personal Information section
Appendix 1. HELM Data Mapping Reference 91
In this section:
Client Templates Mapping ................................................................................. 92
Domain Templates Mapping .............................................................................. 94
* - Plesk Contact name represents the combination of the First Name(s) and the Last Name
defined in Helm administrator‟s Personal Details.
** - As the Personal information in Plesk may contain only one telephone number, the
existing Helm telephone number with the highest priority is migrated. The priorities are
assigned to the numbers by the migration agent during the migration process: the first
priority is assigned to the Daytime Tel., the second one to the Mobile Tel., and the third
one to the Evening Tel.
*** - As the Personal information in Plesk may contain only one e-mail address, the
existing Helm e-mail address with the highest priority is migrated. The priorities are
assigned to the addresses by the migration agent during the migration process: the first
priority is assigned to the Primary E-mail Address, and the second one to the Secondary E-
mail Address.
Templates Mapping
1. What is Template in Plesk?
Plesk Template is a pre-defined set of restrictions and options intended to simplify
creation of new domains (domain templates) and client accounts (client templates)
with automatic assignment of settings to them. Plesk Templates are very close to
Helm Reseller and Hosting plans in function, so Helm Plans are transferred to Plesk
Templates during the migration process.
2. What way Helm Plans are mapped to Plesk Templates?
Parameter values of each Helm Plan (Reseller or Hosting) are divided between two
Plesk Templates: some are transferred to Plesk Client Template, and others to
Domain Template, both having the same name as the name of initial Helm Reseller
or Hosting Plan.
Note: HELM Reseller and Hosting Plans migrate to Plesk if Full migration is performed.
92 Appendix 1. HELM Data Mapping Reference
Client Templates Mapping
Plesk parameter
Value
Origin/Conditions
Template name
Equal to
Plan Name
Plesk parameter
Value
Origin/Conditions
Domain creation
Selected
default
Physical hosting management
Selected if
Web Resource enabled
Hard disk quota assignment
Selected
default
Subdomains management
Selected if
Web Resource enabled
Domain limits adjustment
Selected
default
DNS zone management
Selected if
DNS Resource and DNS Zone Editor
enabled*
Log rotation management
Selected
default
Scheduler management
Selected
default
Anonymous FTP management
Selected if
FTP Resource enabled
Tomcat applications management
Cleared
default
System access management
Cleared
default
Mailing lists management
Selected if
Mail Resource enabled
Antivirus management
Selected
default
Backup/restore functions
Selected
default
Sitebuilder
Cleared
default
To access a list of existing Client Templates, follow these steps:
1 Click Clients in navigation pane.
2 Click the Client Templates button located in the Tools section of the work pane.
To open a page containing information on a certain template, click its name in the
list.
All Client Templates created in Plesk after migration have the properties presented
in the tables below.
Template section
Permissions section
Appendix 1. HELM Data Mapping Reference 93
Plesk parameter
Value
Origin/Conditions
Maximum number of domains
Equal to
Domains
Maximum number of domain aliases
Equal to
Domain Aliases
Maximum number of subdomains
Equal to
Web Resources -> Sub Domains
Disk space
Equal to
Disk space
MySQL database quota
Unlimited
default
Microsoft SQL database quota
Unlimited
default
Maximum amount of traffic
Equal to
Bandwidth
Maximum number of Web users
Unlimited
default
Maximum number of MySQL
databases
Equal to
Database Resources -> MySQL Databases
Maximum number of Microsoft SQL
Server databases
Equal to
Database Resources -> (MSSQL Server
2000 Databases + MSSQL Server 7
Databases)**
Maximum number of mailboxes
Equal to
Mail Resources -> POP3 Accounts
Mailbox quota
Unlimited
default
Maximum number of mail redirects
Equal to
Mail Resources -> Mail Aliases
Maximum number of mail groups
Equal to
Mail Resources -> Multi-Recipient
Addresses
Maximum number of mail
autoresponders
Unlimited
default
Maximum number of mailing lists
Unlimited
default
Maximum number of Web
applications
Unlimited
default
Maximum number of IIS application
pools
Unlimited
default
Maximum number of shared SSL links
Equal to
Web Resources -> Shared SSL
Validity period
Unlimited
default
* - DNS zone management permission value is selected only if both DNS Resource and DNS
Zone Editor were enabled in Helm Reseller/Hosting Plan.
Limits section
** - Maximum number of Microsoft SQL Server databases limit value equals to the sum of
Helm values for MSSQL Server 2000 Databases and MSSQL Server 7 Databases.
94 Appendix 1. HELM Data Mapping Reference
Domain Templates Mapping
Plesk parameter
Value
Origin/Conditions
Template name
Equal to
Plan Name
Plesk parameter
Value
Origin/Conditions
Mail to non-existent user
Bounce
default
Plesk parameter
Value
Origin/Conditions
Maximum number of domain aliases
Equal to
Domain Aliases
Maximum number of subdomains
Equal to
Web Resources -> Sub Domains
Disk space
Equal to
Disk space
MySQL database quota
Unlimited
default
Microsoft SQL database quota
Unlimited
default
Maximum amount of traffic
Equal to
Bandwidth
Maximum number of Web users
Unlimited
default
Maximum number of MySQL
databases
Equal to
Database Resources -> MySQL Databases
Maximum number of Microsoft SQL
Server databases
Equal to
Database Resources -> (MSSQL Server
2000 Databases & MSSQL Server 7
Databases)*
Maximum number of mailboxes
Equal to
Mail Resources -> POP3 Accounts
Mailbox quota
Unlimited
default
Maximum number of mail redirects
Equal to
Mail Resources -> Mail Aliases
To access a list of existing Domain Templates, follow these steps:
1 Click Domains in navigation pane.
2 Click the Domain Templates button located in the Tools section in work pane.
To open a page containing information on a certain template, click its name in the
list.
Domain Templates created in Plesk after migration have the properties presented in
the tables below.
Template section
Mail section
Limits section
Appendix 1. HELM Data Mapping Reference 95
Maximum number of mail groups
Equal to
Mail Resources -> Multi-Recipient
Addresses
Maximum number of mail
autoresponders
Unlimited
default
Maximum number of mailing lists
Unlimited
default
Maximum number of Web
applications
Unlimited
default
Maximum number of shared SSL links
Equal to
Web Resources ->Shared SSL
Validity period
Unlimited
default
Plesk parameter
Value
Origin/Conditions
Enable log rotation
Cleared
default
Plesk parameter
Value
Origin/Conditions
Mailing lists
Cleared
default
Retain traffic statistics
Cleared
default
Plesk parameter
Value
Origin/Conditions
Type of domain DNS zone
Master
default
Plesk parameter
Value
Origin/Conditions
Physical hosting
Selected if
Web Resources enabled
Hard disk quota
Unlimited
default
SSL support
Cleared
default
Microsoft FrontPage support
Selected if
Web Resources -> Frontpage Webs had a
numeric value
Microsoft FrontPage over SSL
support
Cleared
default
* - Maximum number of Microsoft SQL Server databases limit value equals to the sum of
Helm values for MSSQL Server 2000 Databases and MSSQL Server 7 Databases.
Log Rotation section
Preferences section
DNS section
Physical hosting section
96 Appendix 1. HELM Data Mapping Reference
Remote Microsoft FrontPage
authoring
Disabled
default
Microsoft ASP support
Selected if
Web Resources -> ASP had a numeric
value
Microsoft ASP.NET support
Selected if
Web Resources -> ASP.NET had a
numeric value
SSI support
Cleared
default
PHP support
Selected if
Web Resources -> PHP had a numeric
value
CGI support
Selected if
Web Resources -> CGI-BIN had a numeric
value
Perl support
Selected if
Web Resources -> Perl had a numeric
value
Python support
Cleared
default
ColdFusion support
Selected if
Web Resources -> ColdFusion 5/MX had a
numeric value
Web statistics
none
default
Custom Error Documents
Selected if
Web Resources -> Custom Error Pages
enabled
Plesk parameter
Value
Origin/Conditions
Domain name
equal to
Domain Name
Domain Status
Active if
Domain Status was Active
Hosting type
Physical if
Web Resources enabled*
Domains Mapping
All domains registered in Helm migrate to Plesk, regardless of their status
(Active/Disabled) in Helm before the migration (but the status is considered during the
creating a domain‟s records in Plesk, see the table below). The Plesk data concerning
to a domain‟s belonging to a particular Plesk Client depends on the selected source
hosting platform: a domain belongs to a client created on the base of Helm user that
had owned the domain (“Helm (User)” hosting platform), or to a client created on the
base of a Helm reseller that had set up the Helm user owning the domain (“Helm
(Reseller)” hosting platform).
General Information
General information about Plesk domains is presented on the domains administration
page accessible by clicking Domains in the navigation pane. This page contains the list
of all domains existing on the server, which provides the following information on
domains:
Appendix 1. HELM Data Mapping Reference 97
In this section:
Limits................................................................................................................. 98
DNS Zone Settings............................................................................................ 99
Hosting Parameters ........................................................................................... 99
Subdomains ...................................................................................................... 102
Mail ................................................................................................................... 103
Databases ......................................................................................................... 107
Protected URLs ................................................................................................. 108
SSL Certificates ................................................................................................ 109
Additional FTP Accounts ................................................................................... 110
Troubleshooting ................................................................................................ 110
* - If the Web Resources for a domain were not enabled in Helm, then the domain
migrates with non-defined hosting parameters that need to be set up in Plesk
afterwards.
To access a page devoted to a certain domain, click the domain‟s name in the list.
98 Appendix 1. HELM Data Mapping Reference
Limits
Plesk parameter
Value
Origin/Conditions
Maximum number of domain aliases
Correlates
to
Domain Aliases
Maximum number of subdomains
Correlates
to
Web Resources -> Sub Domains
Disk space
Correlates
to
Disk space
MySQL database quota
Unlimited
default
Microsoft SQL database quota
Unlimited
default
Maximum amount of traffic
Correlates
to
Bandwidth
Maximum number of Web users
Unlimited
default
Maximum number of MySQL
databases
Correlates
to
Database Resources -> MySQL Databases
Maximum number of Microsoft SQL
Server databases
Correlates
to
Database Resources -> (MSSQL Server
2000 Databases & MSSQL Server 7
Databases)
Maximum number of mailboxes
Correlates
to
Mail Resources -> POP3 Accounts
Mailbox quota *
Equal to
Max. Mailbox SIze
Some of the limits values for a particular domain default to what is set by Migration
Manager, and some correlate to the limits of a Helm User that created the domain (in
such cases the Value column contains “Correlates to”). The principle of the correlation is
the following: the difference between the total value of a user‟s resource limit* and the
total actual value of a user‟s resource usage** is divided into the number of domains
owned by the user, and the result value is added to the actual value of resource usage
for each domain. The resulting sum is migrated to Plesk as the resource limit value for
a domain. If the result limit value is fractional, then it is rounded up.
* - Total value for a limit equals to the sum of limit‟s values defined in all hosting
packages belonging to the Helm User
** - Total value for a resource usage equals to the sum of actual resource usage values
for all the User‟s domains
To access the page of a certain domain resource usage and other limits, follow these
steps:
1 Click Domains in the navigation pane.
2 Click the required domain name in the list.
3 Click the Limits button located in the Domain section in the work area.
The domain limits data after the migration is the following:
Appendix 1. HELM Data Mapping Reference 99
Maximum number of mail redirects
Correlates
to
Mail Resources -> Mail Aliases
Maximum number of mail groups
Correlates
to
Mail Resources -> Multi-Recipient
Addresses
Maximum number of mail
autoresponders
Unlimited
default
Maximum number of mailing lists
Unlimited
default
Maximum number of Web
applications
Unlimited
default
Maximum number of shared SSL links
Equal to
Web Resources -> Shared SSL
Validity period
Unlimited
default
Plesk parameter
Value
Origin/Conditions
Host
Equal to
Record Name
Record Type
Equal to
Record Type
Value
Equal to
Data
Plesk parameter
Value
Origin/Conditions
Hosting type
Physical if
Web Resources enabled*
* - For Helm 3.2.9 and earlier versions the Mailbox quota parameter is set to
“Unlimited”.
DNS Zone Settings
To view the information on DNS zone for a certain domain, follow these steps:
1 Click Domains in the navigation pane.
2 Click the required domain name in the list.
3 Click the DNS button located in the Services section in the work area.
The domain DNS zone page opens, displaying the list of all DNS resource records
for this domains. The values in this list after the migration are the following:
Hosting Parameters
For each domain migrated to Plesk, the hosting parameters are configured the
following way:
Hosting Type
100 Appendix 1. HELM Data Mapping Reference
Plesk parameter
Value
Origin/Conditions
IP Address
Equal to
Name Server Records**
Certificate
Default
Certificate
default
Plesk parameter
Value
Origin/Conditions
SSL support
Selected if
SSL certificate is installed on domain
FTP/Microsoft FrontPage Login***
Equal to
domain name***
FTP/Microsoft FrontPage password***
Hard disk quota
Unlimited
default
Access to system
Login
disabled
default
* - If the Web Resources for a domain were not enabled in Helm, then the domain
migrates with non-defined hosting parameters, that need to be set up in Plesk
afterwards.
To access the page of physical hosting parameters for a certain domain, follow these
steps:
1 Click Domains in the navigation pane.
2 Click the required domain name in the list.
3 Click the Setup button located in the Hosting section in the work area.
Physical hosting for a domain after the migration is configured the following way:
IP Address section
** - IP Address assigned to a domain in Plesk after the migration is equal to the Helm
Name Server Records value only if the IP address defined in the Name Server Records
really existed in the system. If it did not (that is, it was configured only in Helm), then
the IP Address for a domain is mapped to the server IP, meaning that the IP Address for a
domain is equal to the server IP Address.
Preferences section
Loading...