[Action of the Virtual Machine] Migration

Action of the Virtual Machine

Migration

By using the Migration action, you will be able to change the hypervisor that you selected when you created the virtual machine.

STEP 1: Select the virtual machine
On the left hand menu click on “Virtual Machines”, and select the appropriate virtual machine that you want to migrate from the list.

Select_VM.png

 

STEP 2: Select the migration action
Click “Migrate Virtual Machine” from the Actions section.

Migrate_VM.png

 

STEP 3: Select the hypervisor
Select the desired hypervisor target from the drop down list.

Select_Hypervisor.png

The migration function is yet another advantage of using virtual machines in Cloud computing systems. There are two types of migration function: hot and cold.

Hot migration is the transfer of the OS and applications from hypervisor to hypervisor without stopping OS operations or applications. In a highly demanding environment such as a public cloud, with even the best servers, the risk of failure starts to rise after around 3 years. Our hot migration function easily avoids downtime caused by failure and maintenance issues with physical machines. Hot migration fulfills several needs:

  • Frees up a given physical server for maintenance without downtime for users.
  • Dynamically balances workloads among physical servers so that they all run at optimal levels.
  • Prevents a facility’s under-performing servers (or those on the brink of failure) from interrupting operations.

Cold migration, meanwhile, suspends OS and applications on virtual machines before transferring them to another hypervisor. Types of migration available depend on the hypervisor selected. With cold migration, you have the option of moving the associated disks from one datastore to another. The virtual machines are not required to be on shared storage. The virtual machine you want to migrate must be powered off prior to beginning the cold migration process.

CAUTION: If while making a hot migration, is not successful, time syncrhronization is shifted with the NTP server by 9 hours. This cannot be corrected on our cloud as it is due to the specification of the Windows OS.
Please try to use the cold rather than hot migration.

You may adjust the time in the following way:

1. Login to the. [Remote Desktop].Click on Start Menu> Control Panel> Date and Time
Click the Internet Time tab
2. Click Update Now
setting of 1.2. above 3. If the change is not reflected please try restarting the server from the cloud console.

 

STEP 4: Start of migration
After you choose the migration method and target hypervisor, click “Start Migration”.

Start_of_Migration.png

 

STEP 5: Migration
Migration is initiated, the activity log entry for the virtual server appears. When the log entry status changes from the Running to Complete, then the migration is complete.

Migration_Initiated.png

 

STEP 6: Confirmation of Migration
To confirm that migration has been set can be seen in the Overview properties screen. (In this manual, the Migration has been made to the hypervisor uhv1102 to uhv1101)

Migration_Confirmation.png

 

Note: GMO CLOUD AMERICA INC. does not make any guarantee with regard to the content of this manual and will not be held responsible for any damages resulting from customers or third parties.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk