Parallels Plesk Panel Administrator's Guide
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.
Loading...