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.
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 the [OK] button.
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.
For the selection conditions of VM hosts as the migration target, refer to "Selection of L-Server Deployment Location" in "2.2.3 L-Server" in the "Design Guide CE".
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.
For the selection conditions of VM hosts as the migration target, refer to "Selection of L-Server Deployment Location" in "2.2.3 L-Server" in the "Design Guide CE".
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 overcommit settings.
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.
When performing movement between servers (migration), refer to the chapter of each VM type in "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".
[VMware]
In VMware, migration across clusters is treated as migration across resource pools. Such migration is performed within the same cluster (the same resource pool) because Resource Orchestrator does not manage VMware resource pools.
For details on VMware resource pools, refer to the "vSphere Resource Management Guide" of VMware.
[Solaris Zones]
When an L-Server is located on a VM host with a spare server configured, migration cannot be performed.
When an L-Server is located on a VM host without a spare server configured, migration can be performed to another VM host without a spare server configured that is sharing the disk.
[OVM for SPARC]
Disk resources need to be allocated to all disks of the L-Server when performing migration of an L-Server. Also, the VM hosts which satisfy all of the following conditions are candidates for migration destinations.
VM hosts that are sharing disk resources allocated to an L-Server
VM hosts with the same spare server configuration as the VM host
When an L-Server is migrated to a specified VM host using one of the following methods, after migration the L-Server may not be linked with disk resources, or disk information may not be updated.
Migrating an L-Server between servers from the server tree on the ROR console
Migrating an L-Server between servers using a command and specifying the destination VM host.
When [Automatic] is specified, the L-Server does not migrate to the VM host in which the L-Server (guest domain) which is sharing the disk allocated to the L-Server exists.
When the following VM host is specified as the migration destination for a powered on L-Server, the operation is dependent on the specifications of OVM for SPARC.
A VM host on which another powered on L-Server (guest domain) which is sharing the disk exists
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".
