We currently have separate reservations to split up the SAS datastores from the SSD ones (both tied to the same cluster). We then use two separate blueprints, one that's linked to the SAS reservation policy and one that's linked to the SSD reservation policy. We've noticed that if we storage vmotion a VM that was provisioned from the SAS blueprint over to SSD storage vCAC no longer finds the storage and we see errors during data collection about the VM's storage not being part of the reservation. In managed machines you can't change the reservation as it seems to restrict you to reservations associated with that blueprint. It does appear as though you can change both though. So am I correct in thinking we could just switch the VM to use the other blueprint / reservation? I wasn't sure if anyone's done that or if we're approaching this wrong.
On a similar note if the blueprints have slightly different build profiles and custom properties how does switching blueprints effect the existing VM.
Thanks,
Mike
