[cisco-voip] vMotion w/o Shared Storage

[Anthony Holloway]

Daniel,

Could you give a little more detail about your experience with this
process?  The confusion you faced is likely the same confusion many of us
would face.

Which document(s) did you follow?  Which files did you copy?  What were the
high level steps? etc.

On Tue, Mar 10, 2015 at 9:02 PM Daniel Pagan <dpagan at fidelus.com> wrote:

>  Thanks Dave. I also came across these details, but it too states shared
> storage:
>
>
>
> “A Virtual Machine (VM) file on network/shared storage can be booted on
> any physical server hosting ESXi that has access to that network shared
> storage.”
>
>
>
> But perhaps *my* confusion was vMotion vs cold migration. My original
> thought was using Enhanced vMotion since the objective was to bring the VM
> config and disk to another host and unshared datastore.
>
>
>
> http://www.vladan.fr/vmware-enhanced-vmotion/
>
>
> http://www.ntpro.nl/blog/archives/2118-Enhanced-vMotion-with-vSphere-5.1.html
>
>
>
> I wasn’t sure if this was Cisco supported since all mention of vMotion
> migrations in the VMware requirements document state shared storage, but it
> seems this doesn’t quite fit the process of vMotion (Enhanced or not) since
> the virtual machine is powered off anyway. This would certainly fall under
> the category of cold migration, which is definitely Cisco supported.
>
>
>
> Some confusion on my part between the two migration methods but all is
> clear.
>
>
>
> Thanks!
>
>
>
> - Dan
>
>
>
>
>
> *From:* Dave Goodwin [mailto:dave.goodwin at december.net]
> *Sent:* Tuesday, March 10, 2015 8:47 PM
> *To:* Daniel Pagan
> *Cc:* Ryan Huff; cisco-voip at puck.nether.net
>
>
> *Subject:* Re: [cisco-voip] vMotion w/o Shared Storage
>
>
>
> Keep in mind that moving a VM from one host to another (whether the VM's
> storage is being moved or not) is not considered a vMotion. That is why you
> can do it even without enabling any NICs on the host for the vMotion
> feature. Therefore, the VMWare feature you'd want to look for in the matrix
> is probably "Restart Virtual Machine on Different ESXi Host" and not
> vMotion.
>
> http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements
>
>
>
> On Tue, Mar 10, 2015 at 6:18 PM, Daniel Pagan <dpagan at fidelus.com> wrote:
>
> Thanks - that’s what I figured and just tested with no issues. Seems the
> non-shared storage caveat for vMotion is a non-issue in ESXi 5.1 and
> higher.
>
>
>
>
> http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.vcenterhost.doc%2FGUID-9F1D4A3B-3392-46A3-8720-73CBFA000A3C.html
>
>
>
> I was also concerned of partition alignment but I guess that would be a
> non-issue as well since the vmdk is already provisioned. The move to the
> stand-alone datastore is nearing completion so I’ll double check the start
> block size once it’s done just to be sure!
>
>
>
> - Dan
>
>
>
>
>
> *From:* Ryan Huff [mailto:ryanhuff at outlook.com]
> *Sent:* Tuesday, March 10, 2015 5:08 PM
> *To:* Daniel Pagan; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] vMotion w/o Shared Storage
>
>
>
> Shutdown, yes. Running, no.
>
> Thanks,
>
> Ryan
>
>
>
> -------- Original Message --------
> From: Daniel Pagan <dpagan at fidelus.com>
> Sent: Tuesday, March 10, 2015 05:06 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] vMotion w/o Shared Storage
>
> Quick question…
>
>
>
> vMotion of a shut down UCM between two hosts without shared storage using
> vCenter. Is this supported? The virtualization document for UC platforms
> says vMotion is supported on shared storage, so I figured to ask. Is this
> migration method supported?
>
>
>
> - Dan
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>   _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150311/60884050/attachment.html>