How did you migrate your VM? Did you do VM live migration with storage
migration, or stop VM, migrate disks, then start VM on new storage?
My situation was the first case, the VM was running during migration, so we
knew the disks were available on the new storage. The problem was if we stop
those migrated VM, they could not be restarted due to DB corruption, thus the
need to fix DB to point to correct volumes.
If you migrated your VM like in the second case, then your volume migration
step failed. You should find relevant log entries about volume migration,
hopefully it gives you more info there.
On 3/16/17, 1:31 AM, "Tejas Sheth" <tshet...@gmail.com> wrote:
Hi,
I searched for few documents but in all documents they are mentioning
that VHD will be available on destination storage (but database will point
to source storage)
In our case VHD file is missing from source and destination storage.
