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

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.
JessaymanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jairajnaiduCommented:
please check all drive are in same datastore
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
How was the virtual machine migrated?

This suggests the disks have been wiped, or new disks have been created.
0
JessaymanAuthor 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
0
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
virtual machine disks have been altered of corrupted.
0
JessaymanAuthor Commented:
Exactly so how or what would cause this and am I SoL?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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?
0
JessaymanAuthor 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
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JessaymanAuthor 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
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
JessaymanAuthor 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
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.