This section explains how to move (migrate) an L-Server between servers.
[Physical Servers]
When using physical L-Servers, moving between servers (migration) cannot be used.
[Solaris Containers]
Moving between servers (migration) cannot be performed from the ROR console.
Use the following procedure to migrate between servers:
Right-click the target L-Server in the orchestration tree, and select [Migrate VM Guest] from the popup menu.
The [Migrate an L-Server] dialog is displayed.
Select the destination VM host from the destination VM host list. Only the VM hosts available for migration are displayed in the destination list.
Click <OK>.
From the command-line, execute rcxadm lserver migrate.
For details on the rcxadm lserver migrate command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
Note
Select a destination VM host with available CPU capacity and memory. If there is insufficient CPU capacity or memory, migration between servers or starting of L-Servers may fail.
When specifying [Automatic selection] in the [Migrate an L-Server] dialog, the migration movement differs depending on the value of the [Resource type] for [VM Host] specified when creating the L-Server. This also applies to L-Servers for which overcommit settings have been configured.
When [Automatic] is specified for [Resource type]
The migration is performed with a destination VM host selected from accessible VM pools.
In environments using overcommit, depending on whether or not overcommit settings have been configured for the L-Server, the migration is performed differently as follows:
For L-Servers with Overcommit Configured
The migration is performed with a destination VM host selected from accessible resource pools with overcommit configured.
For L-Servers without Overcommit Configured
The migration is performed with a destination VM host selected from accessible resource pools without overcommit configured.
When [VM Pool] is specified for [Resource type]
The migration is performed with a destination VM host selected from a VM pool.
For environments using overcommit, the same overcommit settings must be configured for both the L-Server and VM pools.
When [VM Host] is specified for [Resource type]
The migration will fail because the destination does not exist. For environments not using overcommit, the same overcommit settings must be configured for both the L-Server and the VM pool which the VM host belongs to.
Perform one of the following:
Select a VM host from the list of the destination VM hosts, and then perform the operation again.
In the [Modify an L-Server] dialog, change the value for "VM host" to "Automatic", and then perform server migration again.
In the [Modify an L-Server] dialog, change the value for "VM host" to "Pool", check the resources to be allocated, and then perform server migration again when necessary.
In the [Modify an L-Server] dialog, change the value for "VM host" to "VM host", check the resources to be allocated, and then perform server migration again when necessary.
If a VM host is specified for the destination VM host, the migration between servers will be performed regardless of whether or not overcommit has been configured.
The information set on the VM host to use can be checked using the following methods:
Select the target L-Server in the orchestration tree, and check "Preserved resource" in the [Resource List] tab
Select the target L-Server in the orchestration tree, and check "Current resource" in the [Resource Details] tab
Maintenance mode excludes the target VM host from the automatically selected target for migration of a virtual L-Server.
Migration by users is possible.
[VMware]
When performing movement between servers (migration), refer to "E.1 VMware" in the "Design Guide CE".
[KVM]
When performing movement between servers (migration), refer to "E.5 KVM" in the "Design Guide CE".
Information
When using virtual L-Servers, the VM Home Position of ROR VE can be used for migration.
For details, refer to "15.3 VM Home Position" in the "User's Guide VE".
