Forced 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

-
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.
When performing movement between servers (migration), refer to the chapter of each VM type in "Appendix E" in the "Design Guide CE".
[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.
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".

17.7.1 Forced Migration between VM Hosts

This section explains the procedure for forced migration between servers of a virtual L-Server operating on a VM host in case the VM
host hardware fails.
This function is supported when using RHEL-KVM.
1.
Items to be checked before executing forced migration
-
Check if VM guest automatic startup settings are disabled on the migration source VM host.
-
The power status of the migration source VM host is in stopped status.
Note
It is necessary to check if the migration source VM host has been stopped. If the VM guest is specified while the migration source
VM host is operating, the L-Server disk data may be damaged as the VM guest will be mounted twice.
2.
Execution of forced migration
Execute the rcxadm lserver migrate command with the -force option specified.
For details on the rcxadm lserver migrate command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
3.
Post processing after executing forced migration
a.
Place the migration source VM host into maintenance mode, complete the hardware maintenance and then delete the VM
guest definitions allocated to the virtual L-Server that was forcibly migrated. Directly delete them from the VM host.
- 223 -

Advertisement

Table of Contents
loading

This manual is also suitable for:

Serverview resource orchestrator cloud edition v3.1.1

Table of Contents