UUID is just an external facing id to reference this volume with from CS
APIs. It isn't used to reference the volume on the hypervisor. That¹s what
path is used for.
Thanks,
-Nitin
On 11/08/14 7:57 PM, Carlos Reátegui create...@gmail.com wrote:
On Aug 11, 2014, at 6:23 PM, Nitin Mehta
Hi All,
Follow-up on my recovery process. After failing to upgrade to 4.4 I did a
fresh install and decided to go ahead and also do fresh installs of
XenServer to upgrade those to XS6.2.
Instead of importing each of the vhd from all my instances as templates and
creating instances from those, I
Carlos - This looks fine to me. Have a couple of questions though
So you reintroduced the old storage pool back on the new MS instance -
make sure the old instances are shutdown and do not access the same
storage else they can corrupt the volumes ?
Did you mean that you changed the path in the
Hi Nitin,
I created a new primary store share in NFS for the new deployment and
removed the old one from exports. The XS hosts where re-used and installed
fresh so nothing was using the old primary store. The new CS deployment
only knows about the new primary store.
I used 'vhd-util scan -f -p
This is superb Carlos. So you created dummy vms to create records in CS db
and then changed the volume path to reflect the old vhds.
Yes, I think it should be fine to delete the dummy vids created with the
new instance.
Thanks,
-Nitin
On 11/08/14 5:49 PM, Carlos Reategui car...@reategui.com
On Aug 11, 2014, at 6:23 PM, Nitin Mehta nitin.me...@citrix.com wrote:
This is superb Carlos.
thank you
So you created dummy vms to create records in CS db
and then changed the volume path to reflect the old vhds.
Exactly.
Yes, I think it should be fine to delete the dummy vids created with
