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 volumes table ?
Thanks, -Nitin On 11/08/14 11:56 AM, "Carlos Reategui" <create...@gmail.com> wrote: >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 created new instances matching the the >previous ones and then edited the volumes table with the vhd of the >original instance from the previous deployment (had to make sure to >include >parent vhd). My volumes were all on shared NFS storage. > >Things appear to be working ok, but want to check if any of you foresee >any >issues with the method I followed. > >thanks, >Carlos