{"id":3143,"date":"2014-06-16T23:03:30","date_gmt":"2014-06-16T15:03:30","guid":{"rendered":"http:\/\/rmohan.com\/?p=3143"},"modified":"2014-06-16T23:35:44","modified_gmt":"2014-06-16T15:35:44","slug":"difference-in-vmware-vmotion-storage-vmotion-svmotion","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=3143","title":{"rendered":"Difference in VMware VMotion & Storage VMotion (SVMotion)?"},"content":{"rendered":"
\n

The differences by VMware VMotion and VMware Storage VMotion (SVMotion) and their benefits.<\/p>\n<\/div>\n

\n

With\u00a0<\/span>VMotion<\/a>, VM guests are able to move from one ESX Server to another with no downtime for the users. What is required is a shared SAN storage system between the ESX Servers and a VMotion license.<\/p>\n

Storage VMotion<\/a>\u00a0<\/span>(or SVMotion) is similar to VMotion in the sense that it moves VM guests without any downtime. However, what SVMotion also offers is the capability to move the storage for that guest at the same time that it moves the guest. Thus, you could move a VM guest from one ESX server\u2019s local storage to another ESX server\u2019s local storage with no downtime for the end users of that VM guest.<\/p>\n

 <\/p>\n

\"vmotion\"<\/a><\/p>\n<\/div>\n

CASE: We had set up a local environment with 1 ESX server. therefore we used local storage for the VM\u2019s. Expansion and the request for DRS and HA brought us to 3 ESX servers and a W2K8 Storage Server as iSCSI SAN. Now we needed to bring the Virtual Machines from local storage to shared storage. This is how I did it:<\/p>\n

1) download and install remote Command Line Interface (RCLI)
\n2) run this code:<\/p>\n

C:\\Program Files\\VMware\\VMware VI Remote CLI\\bin> svmotion.pl \u2013interactive
\nEntering interactive mode. All other options and environment variables will be ignored.<\/p>\n

Enter the VirtualCenter service url you wish to connect to: VCENTER
\nEnter your username: DOMAIN\\USER
\nEnter your password: *****<\/p>\n

Attempting to connect to https:\/\/vcenter\/sdk. Connected to server.<\/p>\n

Enter the name of the datacenter: DATACENTER01
\nEnter the datastore path of the virtual machine: [ESX01:storage1] VMachine01\/VMachine01.vmx
\nEnter the name of the destination datastore: MySAN_LUN0<\/p>\n

You can also move disks independently of the virtual machine. If you want the disks to stay with the virtual machine, then skip this step..
\nWould you like to individually place the disks ? no<\/p>\n

Performing Storage VMotion. 0%
\n|\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014-|100% ################################################################<\/p>\n

Storage VMotion completed succesfully.<\/p>\n

Disconnecting.<\/p>\n

C:\\Program Files\\VMware\\VMware VI Remote CLI\\bin><\/p>\n

 <\/p>\n

 <\/p>\n

VMotion is a non interruptive process, that means while doing the VMotion the VM and the applications running in that VM<\/span>
(GOS) will not get effected.<\/span>

There are 3 types of Migrations are possible from vCenter (VC).<\/span>

VMware VMotion requirements:<\/span>
1. Both the ESX hosts should have the same CPU.<\/span>
2. Both the ESX hosts should have shared storage.<\/span>
3. Both the ESX hosts should have VMkernal port group configured for VMotion.<\/span>
4. Both the ESX hosts using the private network of atleast 1 Gbps for VMotion.<\/span>
5. Both the ESX hosts are added to the vCenter.<\/span><\/p>\n

========================================================================================<\/p>\n

VMotion<\/span><\/p>\n

Migrating a powered-on VM (Virtual Machine) from one ESX host to another ESX host is called the VMotion.<\/span><\/p>\n

\"Vmotion\"<\/a><\/p>\n

VMotion is a non interruptive process, that means while doing the VMotion the VM and the applications running in that VM<\/span>
(GOS) will not get effected.<\/span>

There are 3 types of Migrations are possible from vCenter (VC).<\/span>

VMware VMotion requirements:<\/span>
1. Both the ESX hosts should have the same CPU.<\/span>
2. Both the ESX hosts should have shared storage.<\/span>
3. Both the ESX hosts should have VMkernal port group configured for VMotion.<\/span>
4. Both the ESX hosts using the private network of atleast 1 Gbps for VMotion.<\/span>
5. Both the ESX hosts are added to the vCenter.<\/span><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"\n

The differences by VMware VMotion and VMware Storage VMotion (SVMotion) and their benefits.<\/p>\n

With VMotion, VM guests are able to move from one ESX Server to another with no downtime for the users. What is required is a shared SAN storage system between the ESX Servers and a VMotion license.<\/p>\n

Storage VMotion (or SVMotion) […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[43],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/3143"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3143"}],"version-history":[{"count":4,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/3143\/revisions"}],"predecessor-version":[{"id":3175,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/3143\/revisions\/3175"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}