Migration Between Vm Hosts - Fujitsu ServerView Resource Orchestrator Cloud Edition V3.1.0 User Manual

For infrastructure administrators (resource management) windows/linux
Hide thumbs Also See for ServerView Resource Orchestrator Cloud Edition V3.1.0:
Table of Contents

Advertisement

3.
Click <OK>.
The backup of the system image is deleted.
From the command-line, execute rcxadm image delete.
For details on the rcxadm image delete command, refer to "4.1 rcxadm image" in the "Reference Guide (Command/XML) CE".

17.7 Migration between VM Hosts

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:
1.
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.
2.
Select the destination VM host from the destination VM host list. Only the VM hosts available for migration are displayed in the
destination list.
3.
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.
- 222 -

Advertisement

Table of Contents
loading

This manual is also suitable for:

Serverview resource orchestrator cloud edition v3.1.1

Table of Contents