(Storage vMotion) Source detected that destination failed to resume.

Summary:
I had to script migrate 130+ VM’s off a clariion SAN array because of SP utilization issues to a vMAX array.  All but 3 succeeded.  1 of which exhibited the below symptoms.  The other two were a MSCS cluster, unrelated to this post.
Symptoms:
  1. Above message appears when attempting a Storage vMotion on a VM.
  2. Gets to 5% to 10% before above error appears.
  3. When VMWare’s KB1010045 does not apply as evidenced in my Summary.
Work Around:
  1. vMotion VM to another ESX host.
  2. Attempt Storage vMotion.
    • I have no clue why this worked, but whatever.  If this helps someone make their day a little easier then I’m happy.

Comments

Anonymous said…
I had similar issue, it was failing with same error when moving from a datastore TestSharepoint to datastore TestSharepointMay2010. I renamed the second datastore to TestMay2010 and it completed.
May 7, 2010 at 11:15 AM
Anonymous said…
I was having the exact same problem. Mine would fail at 18%, but all other vm's migrated fine. I moved it to another Host as you suggested and tried again, but it failed at the same spot. After every other possible resolution failed, I decided to move it to yet another host in the cluster and this time I was able to sVmotion it! Thanks!
January 14, 2011 at 12:32 PM
Post a Comment

Popular posts from this blog

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face and get nowhere be
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnect. Using
Read more

Azure VMware Solution: NSX-T Active/Active T0 Edges...but

Image
Summary: Azure VMware Solution (AVS) delivers by default w/ a pair of redundant Large NSX-T Edge VM's each running a T0 in active/active mode.  So why is my traffic only going out one Edge VM? Short answer: The default T1 that is delivered w/ AVS is an active/passive T1 where you connect your workloads to.  So while it could technically take either T0, it's always going to go out the closest T0 to the active "SR" T1.  Where do the SR's live?  You guessed it, on the Edge VM's.  As you can imagine, this can lead to a bottleneck if you try to shove all your traffic through a single Edge VM. Simple Diagram: Longer answer with Options:
Read more