Yeah... this has been an ongoing issue since Mid-December and we finally decided to just rebuild our vCenter server on another host. I went and did the New Virtual Machine stuff and did 'custom' so that I could browse and grab the .vmdk and *_1.vmdk files from our SAN for the disks.
Now, this all worked great on Friday. I come in today... and it's not working. D: drive (*_1.vmdk) is gone, and I can no longer remote to the server. I can't vSphere to it, nothing!
So... we rebuild again, changing the name of the server we just built to _old after shutting it down.
When I go to grab the .vmdk files again, they're... changed? I can't explain it! I have attached a screenshot of what I'm taking about.
Now... is there a way to fix this? And if not, is there a way to regain the information taht was on those files to manage our environment?