Migrating Containers Between Hardware Nodes

The cases when you need to move your Containers from one Hardware Node to another can be quite numerous. A migration can be performed to distribute the workload between Nodes, or in view of an interruption in the source Node operation, and this can be done with the help of Parallels Infrastructure Manager. On the Migrate Container(s) screen you need to select the Hardware Node you are going to move the Container(s) to and select some additional options.

When selecting the destination Hardware Node for you Container(s), remember that you will only be able to migrate Containers between:

• same platform Nodes, so the choice of the destination Nodes that you can pick from the drop-down menu is predefined by the type of operating system the migrated Containers are based on;
• Hardware Nodes registered in Parallels Infrastructure Manager. If you need to migrate the Container(s) to a Node that has not been registered yet, this has to be done first .

In the Live Migration section, choose one of the following migration methods:

• offline migration, stops the Container before migrating, but a possible outage is typically reduced to no more than one minute. To migrate the Container this way, leave the Perform live migration to avoid service interruption checkbox clear;
• online migration, migrates a Container with no interruption in its operation at all. To migrate a Container online, select the Perform live migration to avoid service interruption checkbox;

(For more details on the Container migration types refer to the Migrating Containers section in the Parallels Virtuozzo Containers User's Guide ).

In the Advanced Options section consider the following:

• removing the Container(s) private areas (the directories to store the Container(s) files and other data) from the source Hardware Node when the migration is finished, which lets you free some disk space. On the other hand, you might want to leave the private areas on the source Node intact until you ascertain the migrated Container operates normally;
• leaving the migrated Container(s) stopped to perform some additional operations on it;
• migrating the Container(s) even if their IP addresses might cause conflicts on the destination Hardware Node or if the templates the Containers use are not installed there. Keep in mind that though it is possible to force the migration of such Containers, they might not be able to start on the destination Node until the problems with IP addresses and/or templates are resolved..

Click the Migrate button if you are ready to initiate the Container(s) migration, otherwise click Cancel .

Please send us your feedback on this help page