Tuesday, June 12, 2012 10:59 AM
I'm trying to migrate VM from one cluster to another cluster. Both are Win2008R2 and both use CSV. VM has 1 disk which is placed in C:\ClusterStorage\Volume1\VM. Same destination exist on cluster no2 (C:\ClusterStorage\Volume1). Both storage is set as "Available for placement". Plenty of free space on both of them. When I try to move HA VM from one cluster/storage to another I get following errors:
The host does not have access to sufficient storage of the requested
classification for one or more virtual disks associated with the virtual
Configuration issues related to the virtual hard drive configuration with ID
[xxx] of virtual machine [VM] prevent deployment. ID:23721
If I try to move VM and I uncheck "Make this VM HA" I can move it to C disk (not CSV location). I can move VM to pretty much anything on my LAN EXCEPT to place where I want it and how I want it (Highly available on another cluster and it's CSV).
I'd highly appreciate any help.
- Edited by Dejan Savic Tuesday, June 12, 2012 11:01 AM typing
Wednesday, June 13, 2012 6:55 AM
Just found out that, for some reason, 4 out of 15 VM's on first cluster have storage classification set to "Local storage"!? Those 4 VM's are on the same CSV like other 11 VM's yet they somehow find CSV as local storage. I'll try to find out how to change this but any suggestion from this community is wellcome.
Btw., all 15 VM's were created exactly the same way, they are placed on the same volume of CSV and I see no reason why SCVMM decided to set their storage classification to local storage. I'd accept if it was the case for all VM's or none of VM's, but this is just rediculous!
Friday, June 22, 2012 10:30 AM
Some of servers may done before you add storage pool and storage provider.
Therefore before you added storage to VMM will seem as Local Storage.
After you added Storage, storage classification gets a name and get the Storage pool.
If the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. www.scvmm2012.com (TR Language) Please note that I'm not a Microsoft Representative or SpokesPerson.
Thursday, July 26, 2012 12:34 PM
It might possible be that the "Make VM Highly Available" Checkbox was not selected when the VM's were created, or something of that sort, but the easiest way to resolve the issue, is to look in VMM under which Node / Host the VM that is having its storage as local is running from.
Then Log in to the node, open Failover Cluster Manager, Under Services & Aplications Right Click & Select configure Service or application, select Virtual Machine & Import the VM's from Hyper-V into the cluster, that should mark their storage as shared, and their config as highly available.
Hope this helps, if it does, mark as answer.
Monday, July 30, 2012 7:23 PMModerator
To make a VM highly available, you must locate them on a CSV. VMM will do this for you.
Just migrate a stand alone VM to another node, and mark the VM as highly available. VMM will perform the trick for you, but it will reuire some Down time.
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )
- Marked As Answer by Kristian NeseMVP, Moderator Tuesday, August 07, 2012 6:58 AM