Shared Hosting

The preparation steps vary depending on how you want to migrate:

  • Attach the source hosting servers to CloudBlue Commerce service nodes. This is referred to as takeover migration.
  • Move data from the source hosting servers to CloudBlue Commerce service nodes. This is referred to as full migration.

Preparing for a Takeover Migration

If you want to attach shared hosting nodes to CloudBlue Commerce, you need to do the following:

  1. Update your installation of Odin Business Automation Standard to the latest version, as described in Provider's Guide > Updating Odin Business Automation Standard.
  2. Install and configure the WebHosting Plesk module for CloudBlue Commerce, as described in WebHosting Plesk Provider's Guide > Deploying the WebHosting Plesk Module.
  3. Configure service templates and service plans.
  4. Check if there are domains on the source system that meet the following criteria: they belong to the same user account and a DNS zone of one domain is a parent DNS zone of another domain or domains under the same account. This is a very rare case, but it is possible because there are different buttons in Plesk — Add Domain and Add Subdomain — and users could mistakenly use the wrong option while adding domains and subdomains. The subdomains that were added using the option Add Domain might be migrated without DNS records and might remain active in the source system after migration is finished. For this reason, we recommend that you review all subdomains and re-add all incorrectly registered subdomains by using the Add Subdomain option in Plesk.
  5. Enable DNS forwarding on the source DNS servers managed by Odin Business Automation Standard. Open the file /etc/named.conf and add the following records:

    dnssec-enable yes;

    dnssec-validation no;

    If you do not want to enable DNS forwarding after migration, skip this step and modify the migration tool's configuration file accordingly: on the management node, open the file /opt/oa-migrator/lib/python2.7/site-packages/migrator/settings.py for editing and add the line SKIP_DNS_ZONE_FORWARDING = True.

  6. Make sure that IP addresses used by the source Plesk node for communication and shared IP addresses allocated to the node are not configured as aliases on the network interface. A node can be attached in the takeover mode only by using the first IP address configured on the network interface.

Preparing for a Full Migration

If you want to migrate shared hosting subscriptions to CloudBlue Commerce, you need to do the following:

  1. Update your installation of Odin Business Automation Standard to the latest version, as described in Provider's Guide > Updating Odin Business Automation Standard.
  2. Install and configure the WebHosting Plesk module for CloudBlue Commerce, as described in WebHosting Plesk Guide > Deploying the WebHosting Plesk Module.
  3. Add service nodes and install license keys for them, as described in WebHosting Plesk Guide > Adding Service Nodes.
  4. Make sure that connections to the port 29443 are allowed on Plesk service nodes, and that Plesk service nodes are accessible from the CloudBlue Commerce management node.
  5. Install all the necessary Plesk components on the target web hosting service nodes, as described in WebHosting Plesk Guide > Setting Up Services on Hosting Service Nodes. You must install the same modules and components as the ones used by the source subscriptions: MySQL, Microsoft SQL Server, PostgreSQL database servers, anti-virus solutions, Apache modules such as mod_bw and mod_python, PHP and .NET handlers. You must also activate a PostgreSQL database on web hosting service nodes in CloudBlue Commerce: go to Provider Panel > Services > WebHosting Plesk > Service Nodes > Tools and Settings (in the Actions column) > Database Servers, click the gray icon in the S column (next to PostgreSQL), specify a username and a password, and click OK.

    Warning: If you do not install all the necessary components before migration, and run migration, you will not be able to install the missing components later.

  6. If you want to migrate databases from Microsoft SQL Server, you must ensure that the sqlcmd.exe utility is installed on source and destination servers. To learn more, refer to https://msdn.microsoft.com/library/ms162773.aspx.
  7. Configure IP pools in CloudBlue Commerce. You need to do this only if you choose to use the same types of IP addresses as were used for the source subscriptions. Learn more in WebHosting Plesk Guide > Allocating Dedicated IP Addresses to Service Nodes.
  8. If you want to migrate subscriptions and keep the IP addresses that they are using, configure each source OBAS node as well: Add an IP address to the network interface of each source node and specify this IP address during the registration of the source node in Migration Manager.
  9. Configure service templates and service plans.
  10. Check if there are domains on the source system that meet the following criteria: they belong to the same user account and a DNS zone of one domain is a parent DNS zone of another domain or domains under the same account. This is a very rare case, but it is possible because there are different buttons in Plesk — Add Domain and Add Subdomain — and users could mistakenly use the wrong option while adding domains and subdomains. The subdomains that were added using the option Add Domain might be migrated without DNS records and might remain active in the source system after migration is finished. For this reason, we recommend that you review all subdomains and re-add all incorrectly registered subdomains by using the Add Subdomain option in Plesk.
  11. If you do not want to enable DNS forwarding after migration, modify the migration tool's configuration file accordingly: on the management node, open the file /opt/oa-migrator/lib/python2.7/site-packages/migrator/settings.py for editing and edit the line SKIP_DNS_ZONE_FORWARDING = False. Change False to True.
  12. If you want the Migration Manager to ignore mailbox password errors during migration, open for editing the file /opt/oa-migrator/lib/python2.7/site-packages/migrator/settings.py on the management node and edit the line SKIP_RESTORE_MAILBOX_PASSWORD = False: Change False to True. We recommend doing so to avoid the migration failures that may occur if the mailbox password policy in the target system is more stringent than in the source system. As a result, migration will be carried out regardless of mailbox password errors, but you will be notified of such errors in the end. Note, however, that the contents of all affected mailboxes (for which password errors occur) will not be migrated.
  13. If you do not want to migrate the contents of mailboxes, open for editing the file /opt/oa-migrator/lib/python2.7/site-packages/migrator/settings.py on the management node and edit the line SKIP_MAILBOXES_CONTENT_MIGRATION = False: Change False to True.
  14. If you do not want to migrate email aliases (additional email addresses of mailboxes), open for editing the file /opt/oa-migrator/lib/python2.7/site-packages/migrator/settings.py on the management node and edit the line SKIP_MAILBOXES_ALIASES_MIGRATION = False: Change False to True.
  15. If you do not want to carry over the account balance during migration, open for editing the file /opt/oa-migrator/lib/python2.7/site-packages/migrator/settings.py on the management node and edit the line SKIP_ACCOUNT_BALANCE_MIGRATION = False: Change False to True.

© 2021 Ingram Micro, Inc. All Rights Reserved. Privacy Policy, Terms of Use and Legal