Has anyone tried svmotioning a 2tB LUN? Have you had any issues? Timeouts etc?
I need to svmotion an exchange server over 3 SAN LUN's with 40gig, 750gig and 2 tB. Just wondering how long i should expect it to take! Also how large the snapshot will grow whilst doing the migration
I spit my drink when I read your question.
My goodness - we certainly have not tried one that large, but we do use
smotion a lot. I would be very concerned about the delta file. While
you cannot take our metrics to be exact as there are so many variables.
But the ones we typically do are 50gig VMDK on a 2gig HBA and it takes
about 40 min or so depending on what else is happening on the
host/array. Something that large I would recommend an offline migration
or something. OR..... use something like vmconvertor that does a live
migration of a running system. Smotionn for 2tb..... count me out
Hope this helps
I'm an enabler. You jump first and tell me if the ground is hard
I have done this with a 1TB lun:
- Add a new 1TB drive on the new SAN/LUN
- In windows, make the new drive a mirror of the old drive
- Wait for the mirroring to finish and then destroy the old drive
You'll have to reboot at least once to remove the old drive(s) from the virtual machine, but at least the data got moved safely and without concern for snapshot growth. I forget how long it took, but it didn't really matter.
how do you mirror the 2 seperate LUN's through server 2003? Is it done through disk management or a third party software?
No third party software needed for mirroring. The disks do need to be "dynamic" which might also require a reboot, I don't remember. We have fairly typically set up disks as dynamic from the get-go to allow for these sorts of situations.
Here's some more info:
I've used this technique dozens of times, but svmotion (and akutz's plug-in) have made it basically obsolete, except in cases where you are concerned about snapshot growth.
After upgrading VC to 2.5 build 119598 I get "Failed to connect to host." when I try to SVmotion using the plug-in. Has anyone seen this before? Does SVmotion use the console / vmotion network connections and if so, what port does it use? Or, does it migrate directly to the storage? Also, I'm running SVmotion 1.0 and my hosts are 3.5 U3. Not that U3 has anything to do with it because I have some running U2 that is not working as well.
Hi marvel akutz,
i have one problem, and so far i didnt found it anywhere else described. everytime i try to move virtual disk, or VM, i got error "operation is not supported on the object" and then, VI client crash totally. I am trying to move disk from stand-alone ESX 3.5 local storage RAID5 SAS to NFS NAS storage (on the same switch).
I tried to find some restrictions, and didnt found, if for storage vmotion is needed to have installed Virtual Center, or some another licenses.
I described my situation also at http://communities.vmware.com/message/1099879#1099879, if you are interested. Basicly, i need to move VM out, because i need reformat the VMFS partition, since i added som new hard disks to the RAID5.
i am still learning stuff about advanced maintaing ESX, so be nice ?:|
Or if it is really restricted because of some reason, would it be possible send me some edited "non-production" version to move these VM to NFS? Risk is on my own.;-)
Johnswb, I did something very similar recently. I still can't get it to work from any client workstation but I did install the plugin on my VI server directly and I can now vmotion from there. The plugins just don't work from a remote client.
Every time I try to enable the plug I get: The remote server returned an error: (404) Not Found.
In the meantime I have a workaround.
Just wanted to throw out our thanks for this marvellous tool. We've done nearly 30 SVMotion migrations for files that range from 10 GB to 300 GB without a hitch.
We have been doing these transactions serially, waiting for one to complete before starting the next. Would there be any concern about VMDK fragmentation if we were to start moving files concurrently to the same LUN?
That's really a question for the inventors of SVMotion. The tool
simply calls the right APIs. Glad you like it
Ha, that's absolutely true. I'll check with those in charge of SVMotion on concurrent storage moves.
And if no-one has told you this today let me just say, "YOU ROCK!"
COuld someone please tell me the best site to download the svmotion plugin from
I tested the PlugIn today, and the move worked fine, but the VM still shows that it is occupying something on the source LUN. There is no trace of it on the source LUN that I can see, but the VIC won't see that it only physically exists on the target LUN. This something others have seen? I looked at the trackers and I didn't see anything that was really like this. I did see some stuff about cleaning up, but I don't see any trace of the VM on the source LUN to clean up. Restarted the VIC client a couple times too, and tried it from different machines, and they all show that VM1 is touching LUN1 and LUN2, when it is only really living on LUN2. This is on the 'Summary' tab, btw.
We really need something like this, so thanks for putting the effort into it. I know lots people are appreciating your talents right now