Migrated VM to new datstore now virtual drives are missing or unable to be browsed

Jessayman
Jessayman used Ask the Experts™
on
A virtual machine was migrated to a new datastore and now the drives are unavailable.  When connected into the virutal machine and you access disk management (machine is a 2003 SQL server) the drives required to be initialized.  After drives were initialized assigned a drive letter, drive is unable to be browsed.  I had something like this occur months back and it ended up requiring a rebuild.  Hopefully I can avoid that and would like to try and identify why this is happening.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
please check all drive are in same datastore
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
How was the virtual machine migrated?

This suggests the disks have been wiped, or new disks have been created.

Author

Commented:
Virtual machine was migrated using Vcenter
browsed the datastore and I can identify all the appropiate vmdk's the sizes look accurate
I am now going through the log to identify any potential errors
Should you be charging more for IT Services?

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
virtual machine disks have been altered of corrupted.

Author

Commented:
Exactly so how or what would cause this and am I SoL?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Is all your hardware certified for use with VMware vSphere?

What type of storage?

iSCSI, FC, NFS?

Can you move a test machine and reproduce the fault?

Author

Commented:
hardware is definitely certified (this network supports around 500 navy and contractors)
Storage is netapp -- fiber channel
I have had this issue happen one other time approximately 3 months ago

It would seem that (just looking over my notes) if you have multiple drives attached to a VM that span 2 datastores and then migrate that vm to a new datastore this debacle occurs
  Atleast that is what happened for me it seems
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
I would seriously escalate this into VMware Support and NetApp Support, there appears to be some serious issue with your storage for corruption within the VMDK to be occuring with this equipment.

Author

Commented:
I was afraid you say that as the netapp is definitely the one thing I know little of since I always managed vmware with EMCs.  I also know that upon initial configuration the netapp tech did not complete all his tasks in the days alotted upon purchase, install, and configuration.  Time to hassle netapp support I guess.  Thanks you
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
I've never seen this issue with any storage, HP, EMC, NetApp, Dell etc

If it can be easily reproduced, it will be easy to home in on the issue.

Author

Commented:
I am in the process now of creating a VM associating virtual disks across multiple datastore and seeing if I experience this problem.  That was the first thing I was able to identify in my notes (I maintain a journal since im the vmware admin, DBA, Exchange can be troublesome keeping track) from when I experienced this problem roughly 3 months ago.  I am not wrong though assuming in theory it is fine (maybe not best practice) to have virtual disks from more then one datastore associated with a VM in a HA/DRS configuration
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Completely normal to have virtual machine disks, across different datastores.

you may have different SANs, SSD LUNs, for DB and Logs, but OS LUNs on SATA etc

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial