How vMotion Works ?

What is vMotion?

  • vMotion  enables live migration of a running virtual machine between ESXi Hosts
  • It is transparent to the Virtual Machine’s OS and applications.
  • Invaluable tool to admin to achieve the followings;
    • Avoid Server Downtime
    • Allow Troubleshooting
    • Provide Flexibility
  • Key enabler of DRS, DPM, and FT

vMotion works

What needs to be migrated?

  • Processor and devices state  – CPU, Network, SVGA
  • Disk – Use shared storage between source and destination
  • Memory – Pre copy memory while Virtual Machine is running

How vMotion Works?

  • Quiesce Virtual Machine on source machine.
  • Transfer memory and device state(checkpoint) from source to destination.
  • Resume Virtual Machine on Destination
  • Copy remainder of memory from source to destination
  • Free Virtual Machine resources on source machine.

vMotion Step by Step

Other Interesting Facts, Problems, and Troubleshooting: –

  • Virtual  Machine remains suspended during memory transfer
  • Copying Virtual Machine with large memory size may problematic.
  • 64 GB Virtual Machine requires around 57 seconds on 10 GbE NIC.
  • VMotion will check the remote system to make sure there is enough RAM and CPU before it begins the process.

Troubleshooting: –

  • Migration ID is same on source and destination.
    • Go to VMkernel log (/var/log/vmkernel.log)
    • Grep the migration ID for all vMotion related timing and statistics.

That’s it from here. Stay connected.


Learn SRM – Part 15 – Perform Real Recovery during Disaster Scenario in VMware SRM 6.5

In last article, we saw how to perform a test DR or you can say that Test Drill using Site Recovery Manager.

In this article, we are going to explore a live situation if you face a real Disaster then how will you recover Virtual Machines from Protected Site to Recovery Site.

Step by Step: –

  • Login to Site Recovery Manager Console.
  • Go to Monitor tab under Recovery Plan Section.
  • Click on Red icon.


  • Here you will get a different options. In test recovery, you didn’t had this option. But if you perform a real DR, then you have two options.
  1. Planned Migration
  2. Disaster Recovery
  • If you want to perform a real recovery during any Disaster, you have to choose option 2 which is for Disaster Recovery scenario.
  • Accept Recovery Confirmation and Click on Next.

2018-08-28 01_18_53-vSphere Web Client

  • Disaster Recovery is ready to start. Click on Finish.

2018-08-28 01_19_31-vSphere Web Client

  • Real Recovery has been started. You can monitor the status of recovery here .

2018-08-28 01_20_53-vSphere Web Client

So that’s all from VMware Site Recovery Manager module. We are closing this module here. If you have not gone through with earlier articles, please go through with that to get a detailed information on VMware SRM. I will come back with the new topic next week. Stay tuned to Cloud Pathshala.

Once again Thank you so much for being part of Cloud Pathshala and visiting here. Do share you inputs in comment box. If you want to add on here, send us email at Follow us on our social media platform to stay updated and get notification for any new article. You can find us any platform at @CloudPathshala. You can subscribe our Youtube change at

If you found this module or article useful, please do share with your friends. I will say a good bye for now. Let’s meet again in next module on different topic.

Take a look in below topics, explore and learn Site Recovery Manager: –

Learn SRM – Part 14 – Perform Cleanup Activity in VMware SRM 6.5

Once our Testing has been completed, we need to run cleanup of the environment. Site Recovery Manager performs several cleanup operations after a test.

  • Powers off the recovered virtual machines.
  • Replaces recovered virtual machines with placeholders, preserving their identity and configuration information.
  • Cleans up replicated storage snapshots that the recovered virtual machines used during the test.

Step by Step: –

  • Login to VMware Site Recovery Manager Console.
  • Go to Monitor Tab and Click on icon highlighted in Red box.

2018-08-28 01_17_31-vSphere Web Client

  • Ready the Informational message. you may also choose Force Cleanup option if normal cleanup doesn’t work properly.
  • Click on Next

2018-08-28 01_17_34-vSphere Web Client

  • Cleanup Activity is ready to complete. Click on Finish to start the activity.

2018-08-28 01_17_40-vSphere Web Client

  • Monitor the Status of Cleanup Activity.

2018-08-28 01_17_44-vSphere Web Client

  • Cleanup has been done. Status is again in Ready State now. You can see the Green Run icon has been highlighted.

2018-08-28 01_18_18-vSphere Web Client

That’s all about Cleaning up our environment after Test Disaster Recovery. I will also add one more article which will show you how to Perform Recovery during Real Disaster. Stay Tuned to next article.

Take a look in below topics, explore and learn Site Recovery Manager: –