The snapshot won't be a set of files that you can view. It will be a copy of exactly what the LUN looked like when you took the snapshot, so you'll need to mount it in vSphere just like you would mount the regular LUN. Then you'll see all the VMX and VHDX files for the VMs that you snapshotted. Then you can add one into vSphere and power it on to get its files back. Keep in mind that you'll want to disable all networking on that VM so that it doesn't conflict with the real VM on the network.
Another newbie problem.  I've learned alot about my new Virtual world and the Dell Equal Logic box.  But, I still have one fundamental problem that has to be an easy fix or something that I just don't understand technically.  I want to be able to connect to a snapshot and be able to go in and grab a file if needed. I brought the snapshot online and I even was able to mount it in vSphere so I could see it there.  But, for the life of me I can't get any iscsi initiator to see the snapshot at all.  I have some guesses, but I can't seem to figure out my problem. I cannot get the initiator to see any targets...it just tells me the connection fails.  I think I know why, but my networking skills are not real strong.  When we had an outside company come in and install the environment, they put everything on 192.168.100.x or 192.168.101.x.  Ever since I got here (over 15 years ago), our network has always been 129.1.x.x ip addresses.  I am programmer for the most part and I have a networking guy who is solid at networking but I am not sure if he can answer my question either. Anyway, when I try to add my target portals in the initiator, what IP address or name am I supposed to be pointing to?  I can't ping the 192 addresses because I am on a 129.1.x.x ip, correct?  So, is that why I have no chance of finding snapshots using the initiators?  I know the vCenter server has a 129 address and the SAN itself has a 129 address and I have tried to connect to those but that hasn't worked. I believe I have given permission to the snapshot to be seen by multiple initiators. I think it is my lack of networking, but maybe not.  Any help would be greatly appreciated.    Thanks, Ryan Kotowski
ISCSI Initiator problem