2 Replies Latest reply on May 13, 2019 1:01 PM by Darking

    Failed migration of VM to vsan, could it be a vmdk naming issue?

    Darking Novice

      i tried to migrate at largish fileserver (5.5TB) to vsan on friday, but it failed twice doing so.

       

      and im wondering if my issue is due to multiple vmdks with the same name?

       

      the server has 5 disks.

       

      disk one is located on datastore A and is called fileserver.vmdk

      disk two is located on datastore A and is called fileserver_1.vmdk

      disk three is located on datastore B and is called fileserver.vmdk

      disk four is located on datastore C and is called fileserver.vmdk

      disk five is located on datastore D and is called fileserver_5.vmdk

       

      is that an issue for vsan, or should it be able to handle this during a migration?

       

      tdlr: 5 disks, 3 of which has the exact same vmdk name. is it an issue to migrate to vsan?