2020. 2. 23. 07:56ㆍ카테고리 없음
.Select the hosting panel installed on the source server from thePanel type menu.Specify the following:. The source server’s IP address. If migrating from a Linux server,specify the SSH port as well (22 by default).
(Plesk for Linux) The login and password of a root user on thesource server. Alternatively, you can choose to authenticate viaSSH keys. For details, refer to. (Plesk for Windows) The login and password of the built-inadministrator accounts on both the source and the destinationservers. The directory for storing temporary files on the source server(make sure there is enough free disk space available to store thedump of the largest database that will be migrated).If migrating from a Windows-based server, specify the method forinstalling the RPC agent (an application enabling Plesk Migrator togather data):. Automatic (recommended).
Plesk Migrator will try to deploy andstart RPC agent on the source server using the built-inadministrator account. In some cases, automatic deployment mayfail (for example, due to firewall settings, or because the Fileand Printer Sharing or RPC services are disabled). If thishappens, deploy the agent manually.
Manual. A link to download the RPC agent package will beprovided. Download the package and install the agent on the sourceserver manually.Click Prepare Migration to proceed to the next step. PleskMigrator will attempt to fetch the data about the different objects(domains, subscriptions, customer/reseller accounts, and hostingplans) found on the source server.
If the connection fails,double-check the source server information, make sure that theconnection is not blocked by firewall, and try again.Note that from this point onwards, you can leave the Migratorinterface without losing your progress - the migration will remain inprogress until you finish it explicitly. To continue from where youleft off, click Server Management Extensions PleskMigrator and then click the corresponding migration in the list. Here you must select the subscriptions to be migrated (note that youcannot migrate individual domains, the fewest number of objects youcan migrate is a single subscription and all its domains). You canuse one of four available filters:. By Subscription. If you migrate a subscription owned by acustomer or a reseller, the corresponding customer/reselleraccount will be migrated as well (unless a custom subscriptionowner is specified - see below).
Windows To Linux Migration
The hosting plan the subscriptionis based on will also be migrated. By Customer. If you migrate a customer account, allsubscriptions owned by the account will be migrated together withthe hosting plans they are based on. By Reseller. If you migrate a reseller account, allsubscriptions owned by the account will be migrated together withthe hosting plans they are based on.
Note that migrating areseller account does not automatically migrate the customeraccounts owned by the reseller. If you select a reseller accountand one or more customer accounts owned by that reseller formigration, the reseller’s ownership of the customer accounts willbe preserved on the destination server. By Hosting Plan. If you migrate a hosting plan, allsubscriptions based on the said plan will be migrated as well.
Ifyou migrate a hosting plan belonging to a reseller, said resellerwill be migrated as well, plus all subscriptions based on theselected hosting plan together with the customers who own thosesubscriptions.Select what types of content (mail content, web content, anddatabases) will be migrated.Select a custom subscription owner. By default, whenever asubscription owned by a customer or reseller is migrated, thecorresponding customer or reseller account is created on thedestination server as well. If you select a different subscriptionowner, the ownership of all subscriptions being migrated will beassigned to that account.To change the migration settings, click Settings in theupper-right corner. Here, the following controls are available:.
Adjust application settings. By default, during migrationPlesk attempts to make changes to the configuration files of anumber of popular web applications to make them operable on thedestination server. Clear the checkbox if you want to make thechanges manually.
Leaving this option enabled will increase themigration time. Apache restart interval (Plesk for Linux only). Restarting theweb server on the destination server is necessary for the migrateddomains to become available over the network. Make sure not to setthis value too low (less than 300 seconds is not recommended), asall hosted domains become temporarily unavailable every time theweb server is restarted.
Run post-migration checks. By default, after the migration isfinished, Plesk performs a number of automated tests to identifypotential issues with the migrated domains.
Clear the checkbox ifyou do not want the tests to be run. Leaving this option enabledwill increase the migration time.When you are satisfied with the list of subscriptions to migrate andthe migration options, click Migrate to proceed. Plesk will runpre-migration checks to detect potential issues and display a report. The icon indicates that the migration wascompleted successfully. The icon indicates that the migration wascompleted with errors. Click Details to see the list ofissues that occurred during the migration. The icon indicates that the migration failed.Click Details to see the list of issues that occurred duringthe migration.If you want to perform an additional sync of a subscription’s contentafter the migration is finished, click Re-sync next to thesubscription’s name.If you want to migrate additional subscriptions from the sourceserver, return to step number seven.
Otherwise, unless you plan tomigrate from the same source server again in the near future, you canclick Finish migration to remove it from the list of ongoingmigrations.