Problems with Storage DRS

[martiniervasi]

Hi all.

I have randomly problems when Storage DRS runs automatically over the cluster. The problem does not happens when the VMs are migrated manually.

The problem is that migration fails and the VM´s VMX files gets migrated but does not migrate the VMDK files. These cause the VMs to loose the location of the VMDK files, the VM reboots and print does not locate the SO Disk.

In the logs I detected the following.

(Extract from the Log)

2013-03-08T06:07:29.299Z| vcpu-0| I120: Msg_Post: Error

2013-03-08T06:07:29.299Z| vcpu-0| I120: [msg.disk.notCheckpointed3] Resuming virtual disk scsi0:0 failed. The disk has been modified since a snapshot was taken or the virtual machine was suspended.

2013-03-08T06:07:29.299Z| vcpu-0| I120: [msg.checkpoint.continuesync.error] An operation required the virtual machine to quiesce and the virtual machine was unable to continue running.

I am attaching the full logs.

Thanks in advance!

[pscheri]

I am working with Martin in this issue.

This is now also happening with manual Storage vMotion.

Regards,

Pablo.-

[Linjo]

Are you using VMware View?

// Linjo

[pscheri]

Yes, this is View 5.1.1 and vSphere 5.1 almost last updates.

[Linjo]

Ok, that explains it.

Storage vMotion and Storage DRS is not supported with VMware View.

Use the rebalance-funtionality in View instead to redistribute the linked clones.

// Linjo

[ShakespearsGhos]

As stated in the View Documentation, http://pubs.vmware.com/view-52/topic/com.vmware.view.administration.doc/GUID-B498C846-C7FE-4D37-9899..., Storage vMotion is not supported for moving View Linked Clones. 

[pscheri]

Hi, thanks for the quick response, this is not working with View Composer, all the VMs are full VMs.