Search Engine: Elastic

Article ID: 129830, created on Nov 9, 2016, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0


During precheck operations, the following error message appeared:

There are websites on the node where the brand is hosted: <list>
Do the following: Move these websites to another node or move brand(s) to a separate host before upgrading to 7.0.
<site> on host <branding node hostname>

The following instruction will guide through the process of website transfer between nodes.


In OA 7.0 branding was redesigned and does not allow usual hosting subscriptions to present on the branding node. These subscriptions should be transfered to webhosting nodes.


Currently there is no way to perform automated migration of webspace between standalone Linux NG nodes. So the procedure includes manual operations that could be divided into three parts: subscription provisioning, content backup and content restoration.

Important notices:

  1. Siteapps that installed on the website will not be transferred. To handle this case, please contact Odin Technical Support.

  2. IP-address of website will not be preserved. You will need to replace it with new one, if IP address is configured somewhere inside the website content.

Please, follow the steps below to transfer website (assume: brandsite.local) from branding node to webhost:

  1. Mark branding node as "Not ready to provide".
  2. Provision new webhosting subscription on the same or similar configuration Service Plan. Let's assume, it was provisioned on webhost.
  3. Ensure that subscription is provisioned provisioned to webhost by navigating to PCP -> Service nodes -> webhost -> Customer Services tab.
  4. Login to branding and navigate to webspace directory, (let's assume: /var/www/vhosts/3/100010/webspace/httpdocs/brandsite.local).
  5. Create backup of webspace content (ensure that destination has enough free space):

    # tar czvf /tmp/brandsite.local.tar.gz *
  6. Login to CCP, switch hosting to new subscription by navigating to Websites -> brandsite.local -> View details and pressing Change Hosting button.
  7. Transfer archive with webspace content from branding to webhost by any means possible.
  8. Login to webhost, navigate to newly provisioned webspace directory (let's assume: /var/www/vhosts/2/100015/webspace/httpdocs/brandsite.local).
  9. List file attributes and note their owner:

    # ls -l
    -rw-r--r-- 1 w100015 pemcln    43 Nov  7 17:53 1x1.gif
    -rw-r--r-- 1 w100015 pemcln 17688 Nov  7 17:53 banner.gif
    -rw-r--r-- 1 w100015 pemcln  2460 Nov  7 17:53 company_logo.png
  10. Restore content from backup to webspace directory on webhost:

    # tar xf brandsite.local.tar.gz
  11. Restore ownership of files using owner name from step 9:

    # chown w100015:pemcln *
  12. (Optional) Cancel old hosting subscription, under which website was hosted before transfer. If not, content of the website will be left intact on branding host and precheck will be sucessfull.
  13. Mark branding node as "Ready to provide".

After these steps website brandsite.local should be fully functional under its new location on the webhost and precheck procedure should no longer throw corresponding error.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF