UNSOLVED
Understanding applications and LUN usage
I'm trying to understand specific examples of how information on LUNS are seen/used by the end user. Could you please provide sepcific examples of how an end user gets/uses data stored on a LUN? If you could describe the process from end user to the host, to the switch, to the LUN, that would be awesome. As much detail as possible would be great! I'm trying to understand specific examples, not conceptuals (i if it is saide On any server (what server?) there are various mechanisms to control what devices an application (what is an example of an application) can see and whether or not the application can talk to another device (what device?) As much detail as possible would be great!
Hi Karl,
Thank you for the information. For a bit of a further explanation, let's say I have a Windows host that is connect through a switch to a Clariion. I format the disk on the Windows host as the Z drive.
I have 50 users that need access to the Z drive, how is that informaiton seen by the users?
Also, how is it set up to allow those users to see the drive? (I'm not referring to zoning and masking, just how is it set up from the Windows host to the users.)
christopher_ime
6 Operator
•
1962 Posts
294
0
Posted November 26th, 2012 01:00
zaboo9,
Once it is assigned a local drive letter, at this point it is standard Windows file sharing.
umichklewis
4 Apprentice
•
1190 Posts
294
1
Posted November 20th, 2012 14:00
Sounds like you're looking for answers to a storage management test or exam.
A quick Google search turned up several examples, as well as a nice article on wikipedia. Assuming you've read either, you see that a LUN is typically seen by an end user as a "disk" in Windows. That disk can be formatted with a filesystem, which will allow the end user to create files and folders. As a LUN is a "disk", once a disk is accessible to the host, host-based controls (POSIX ACLs or Windows permissions) are used to control access to files and folders. Applications are bound by the same restrictions as users (again, permissions).