Method and apparatus for encapsulating a virtual filer on a filer

RELATED APPLICATION

[0001] This application is a continuation of U.S. patent application Ser. No. 10/035,664, entitled ARCHITECTURE FOR CREATING AND MAINTAINING VIRTUAL FILERS ON A FILER, by Mark M. Muhlestein, et al.

FIELD OF THE INVENTION

[0002] The present invention relates to server architectures and, more specifically, to an architecture that enables instantiation of multiple logical servers within a single physical server platform.

BACKGROUND OF THE INVENTION

[0003] A file server is a computer that provides file service relating to the organization of information on writeable persistent storage devices, such memories, tapes or disks. The file server or filer may be embodied as a storage system including a storage operating system that implements a file system to logically organize the information as a hierarchical structure of directories and files on, e.g., the disks. Each “on-disk” file may be implemented as set of data structures, e.g., disk blocks, configured to store information, such as the actual data for the file. A directory, on the other hand, may be implemented as a specially formatted file in which information about other files and directories are stored.

[0004] A storage system may be further configured to operate according to a client/server model of information delivery to thereby allow many clients to access an application service executed by a server, such as a file server. In this model, the client may comprise an application executing on a computer that “connects” to the file server over a computer network, such as a point-to-point link, shared local area network, wide area network or virtual private network implemented over a public network, such as the Internet. Each client may request the services of the file system on the file server by issuing file system protocol messages (in the form of packets) to the server over the network. It should be noted, however, that the file server may alternatively be configured to operate as an assembly of storage devices that is directly-attached to a (e.g., client or “host”) computer. Here, a user may request the services of the file system to access (i.e., read and/or write) data from/to the storage devices.

[0005] One type of file system is a write-anywhere file system that does not overwrite data on disks. If a data block on disk is retrieved (read) from disk into memory and “dirtied” with new data, the data block is stored (written) to a new location on disk to thereby optimize write performance. A write-anywhere file system may initially assume an optimal layout such that the data is substantially contiguously arranged on disks. The optimal disk layout results in efficient access operations, particularly for sequential read operations, directed to the disks. An example of a write-anywhere file system that is configured to operate on a storage system, such as a filer, is the Write Anywhere File Layout (WAFL™) file system available from Network Appliance, Inc., Sunnyvale, Calif. The WAFL file system is implemented as a microkernel within an overall protocol stack of the filer and associated disk storage.

[0006] The disk storage is typically implemented as one or more storage “volumes” that comprise a cluster of physical storage devices (disks), defining an overall logical arrangement of disk space. Each volume is generally associated with its own file system. In the WAFL file system, a special directory, called a “qtree”, may be created that has the properties of a logical sub-volume within the namespace of a physical volume. Each file system object (file or directory) is associated with one and only one qtree, and quotas, security properties and other items can be assigned on a per-qtree basis. Each volume has its own file system identifier (ID) and each qtree within a volume has its own qtree ID.

[0007] A filer typically includes a large amount of storage (e.g., 6 terabytes) with the ability to support many (thousands) of users. This type of storage system is generally too large and expensive for many applications or “purposes”. Even a typical minimum storage size of a volume (or file system) is approximately 150 gigabytes (GB), which is still generally too large for most purposes.

[0008] Rather than utilizing a single filer, a user may purchase a plurality of smaller servers, wherein each server is directed to accommodating a particular purpose of the user. However, there is still the granularity of storage issue since, as noted, the typical minimum storage size of a volume is approximately 150 GB. In addition, the acquisition of many smaller servers may be more costly than the purchase of a single filer. Furthermore, the cost of maintenance and administration of many smaller servers is typically substantially more than the cost of maintaining and administering a single filer. Therefore, it would be desirable to consolidate many servers within a single filer platform in a manner that logically embodies those servers. Server consolidation is thus defined as the ability to provide multiple logical or virtual servers within a single physical server platform. Examples of virtual servers that may be embodied within a single platform are web servers, database servers, mail servers and name servers.

[0009] Prior server consolidation solutions provide many independent servers that are essentially “racked together” within a single platform. An example of this solution is the Celerra™ architecture available from EMC® Corporation. The Celerra architecture utilizes the notion of a data mover or an instance of a file server that “front ends” a Symmetrix® storage device having storage resources that can be logically apportioned and assigned to various other data movers. Each data mover has its own set of networking hardware and its own processor running its own copy of the operating system.

[0010] Other server consolidation solutions are configured to run multiple instances of a server on a single physical platform. For example, the virtual machine (VM) operating system from IBM® Corporation executes on a mainframe computer system and enables execution of multiple instances of servers on that computer system. Each VM is a complete instantiation of an entire operating system having its own file system and storage resources. That is, there is no sharing of file system and storage resources among the VMs operating on the mainframe. Rather, the storage resources of the computer system are apportioned and dedicated to instances of VMs embodied on the computer.

[0011] Another example of a server consolidation solution adapted to run multiple instances of a server process is Samba. Samba is an open-source Windows-compatible server running on a UNIX operating system platform. The Samba server is implemented at the application layer of the system to provide multiple instances of Windows-compatible servers running on the UNIX platform. Samba is an example of a more general “server process replication” based approach for implementing multiple servers on a single physical platform.

[0012] Finally, the simplest method of implementing server consolidation is to rename all service (i.e., storage for file servers) units being consolidated such that they are unique among themselves and to configure one instance of the consolidated server that serves all of the service (storage) units. This technique is hereinafter referred to as “server bundling”.

[0013] Process-based and server bundling-based server consolidation solutions typically do not provide different security characteristics for each of the server instances running on the platform. For example, Samba has only one set of security characteristics (i.e., a security domain) pertaining to non-replicated parts of its platform infrastructure for all of its instances of Windows-compatible (e.g., NT) servers. An example of a security dos main is the Windows NT™ domain security. The NT domain security is an abstraction whereby all users and servers of a domain share the same security information, which may include authorized user and group identifiers (“security objects”) and resources of an operating system.

[0014] Broadly stated, the security information is maintained in a security account manager (SAM) database by a Windows NT protected subsystem. The SAM database is equivalent to a combination of /etc/passwd and /etc/group databases on a UNIX® server in that it contains only users and groups local to that server. The notation /etc/passwd, /etc/group denotes a configuration directory indicating a path to a password file and a group file used on the UNIX platform. A user with an account in a particular security domain can log onto and access his or her account from any server in the domain. Typically, one server can be in one security domain (for each access protocol) at a time. Multi-protocol servers can be in as many as one security domain for each access protocol. For example, a multi-protocol filer may be in an NT4 domain for Common Internet File System (CIFS) access and in a Network Information System (NIS) domain for Network File System (NFS) access. As mentioned above, UNIX environments also have security objects that may be different for different servers.

[0015] An aspect of Windows™ networking is the notion of a uniform naming convention (UNC) path that defines a way for a user to refer to a unit of storage on a server. A UNC path is prefixed with the string \\ to indicate resource names on a network. For example, a UNC path may comprise a server name, a share name and a path descriptor that collectively reference a unit of storage, such as a share. A share is a shared storage resource, such as a directory on a file system.

[0016] In an environment having multiple independent servers used to accommodate multiple security domains, all shares (and share names) must be distinct. However, if those servers are consolidated onto a single platform (by way of server process replication, such as Samba, or server bundling) using alias names for the server, the server names of the UNC paths to the shares may require change, since all share resources would be visible when accessed via any of the alias server names. In other words, although each server may have its own set of shares, users may have to change the UNC path definitions of those shares in order to access their data.

[0017] For example, assume that three (3) NT servers are organized such that a first NT server (NT1) and its clients are associated with security domain 1, while second and third NT servers (NT2, NT3) and their clients are associated with security domain 2. Thus, the clients (users) of NT2 and NT3 share the same security database within security domain 2. If a user of domain 2 refers to a particular share (proj1) on NT3, it first attaches to security domain 2 in order to authenticate and then attaches to the server and share on that server. An illustrative example of the notation of the UNC path specified by the user is:

[0018] \\NT3\data\proj1

[0019] Assume now that the servers NT1-3 and their attached resources are consolidated onto one server platform. This raises the issue as to how the clients of a particular domain refer to their data. That is, if each client has a share called proj1 and all of the shares are consolidated within a single platform, there must be a way to differentiate those shares. Migration and reconfiguration of data on storage resources of a server is typically not transparent to a client system; in fact, this issue is often resolved by requiring the client system to change its path descriptor to its data. Such an approach is generally undesirable because it requires action on behalf of the client system. Moreover, if the storage resources are consolidated on one or more servers, it is possible that those servers may not be in the same security domain as the users accessing those resources.

[0020] The VM and data mover server consolidation techniques, which are based on partitioning of physical system resources and replication of operating system objects, do not suffer from the two above-mentioned limitations of not being able to consolidate servers from multiple security domains or requiring service (storage) unit renaming. However, these techniques do have other limitations. The operating systems of such server consolidation solutions typically contain software objects that are representative of physical hardware devices, such as network interface cards or well-defined collections of hardware devices. An example of a software object representative of a collection of hardware devices is a file system that allocates space on a set of storage disks available for use by applications running on the operating system.

[0021] In a VM or data mover type of system, a static assignment of these hardware representative software objects is typically performed to associate a subset of the hardware resources of the system with a single instance of a VM/data mover (virtual server). The assignment of resources to each virtual server results in hardware resources being directly associated with the specific virtual server, because the software objects that represent these hardware resources are directly assigned to the virtual servers. This direct assignment approach restricts resource management flexibility, particularly with respect to “logical” reassignment of resources among the virtual servers. This also hinders evolutionary growth of the server consolidation implementation because all partitioning and sizing decisions must be made at the time of consolidation and cannot be easily changed later as the consolidated servers evolve.

[0022] Server consolidation is particularly useful in the case of a storage server provider (SSP). An SSP serves (“hosts”) data storage applications for multiple users or clients within a single, physical platform or “data center”. The data center is centrally maintained by the SSP to provide safe, reliable storage service to the clients. In a typical configuration, the data center may be coupled to a plurality of different client environments, each having an independent private internal network (“intranet”). Each intranet may be associated with a different client or division of a client and, thus, the data traffic must be separately maintained within the physical platform.

[0023] Therefore, the present invention is directed to an architecture that enables instantiation of multiple, secure virtual servers within a single physical filer platform that allows flexible partitioning of physical resources.

[0024] The present invention is also directed to an architecture that enables instantiation of multiple, secure virtual servers within a single physical filer platform that is suitable for use in an SSP environment and that provides a high level of security for users.

[0025] The present invention is further directed to an architecture that enables encapsulation of a server, including its data and all its configuration information, stored in a form that allows efficient migration and re-instantiation of the server on a different physical platform for use in disaster recovery, data migration or load-balancing.

SUMMARY OF THE INVENTION

[0026] The present invention relates to an architecture that provides the ability to create and maintain, with substantial flexibility and fine granularity, multiple instances of virtual servers, such as virtual filers (vfilers), within a server, such as a filer platform. A vfiler is a logical partitioning of network and storage resources of the filer to establish an instance of a multi-protocol server. Each vfiler is maintained and executed independent of other vfilers on the platform. Dedicated filer resources, such as units of storage and network addresses of network interfaces, may be grouped and partitioned to establish security domains within the filer. Yet common filer resources, such as a storage operating system and a file system, may be shared among the vfilers.

[0027] Specifically, each vfiler is allocated dedicated and distinct units of storage resources, such as volumes or qtrees, and network addresses, such as Internet protocol addresses. Each vfiler is also allowed shared access to the common file system on behalf of its client system. Therefore, interpretations of a security object associated with, e.g., a client accessing the common file system may vary among vfilers. To address this, each vfiler is provided a vfiler context data structure including, among other things, information pertaining to a unique and distinct security domain of the vfiler (for each supported access protocol) to thereby enable controlled access to allocated and shared resources of the vfiler.

[0028] According to an aspect of the present invention, a vfiler boundary check is performed by the file system of the storage operating system to verify that a current vfiler executing on the filer is allowed to access certain storage resources for a requested file stored on the platform. The vfiler boundary check is based on configuration information, such as the unit of storage (qtree or volume) associated with the file, acquired from an inode of the requested file. Specifically, a file system identifier and qtree identifier are validated in accordance with a multi-stage verification procedure to ensure that they are members of the storage resources allocated to the current vfiler. For every request to access a unit of storage, the boundary check is performed using these identifiers to determine whether the requesting vfiler is authorized to access the storage resource. If the check reveals that the vfiler is not authorized to access the requested storage resource, the request is immediately denied. Otherwise, the request is allowed and the file system generates operations to process the request.

[0029] Advantageously, the novel vfiler architecture facilitates both consolidation of virtual servers and their respective data applications on a single filer, as well as encapsulation of all server network and storage resources. Server consolidation is achieved through the creation of vfilers, each of which is associated with a security domain (one for each supported access protocol). The security domains are completely disjoint, thereby providing separate and independent vfilers within the same filer platform. This aspect of the invention is particularly useful in the case of a storage service provider, wherein the data applications of multiple client organizations are hosted on the filer. Each client organization can access only its own vfiler and is entirely unaware that it is sharing the same physical filer with other organizations. The novel architecture thus obviates the need to dedicate a filer for each client organization.

[0030] Moreover, migration of storage resources between and among vfilers is transparent to clients since the storage resources are allocated on a per-vfiler basis. This obviates the need for a client to change the way (e.g., path descriptor) it refers to its data. Additionally, since the underlying file system is shared, the assignment of storage units to vfilers can be managed flexibly and with fine granularity. That is, a single volume can be shared by multiple vfilers; furthermore, a single filer can own one or more volumes and/or one or more qtrees on any of several volumes.

BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The above and further advantages of the invention may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numerals indicate identical or functionally similar elements:

[0032]FIG. 1 is a schematic block diagram of a computer network including a plurality of clients and a server that may be advantageously used with the present invention.

[0033]FIG. 2 is a schematic block diagram of a server, such as a network storage appliance or filer that may be advantageously used with the present invention;

[0034]FIG. 3 is a schematic block diagram of a storage operating system that may be advantageously used with the present invention;

[0035]FIG. 4 is a schematic diagram of an embodiment of a filer having a plurality of virtual filers (vfilers) in accordance with the present invention;

[0036]FIG. 5 is a schematic block diagram illustrating a vfiler context data structure in accordance with the present invention;

[0037]FIG. 6 is a schematic block diagram illustrating soft object data structures that may be advantageously used with the present invention;

[0038]FIG. 7 is a schematic block diagram illustrating various data structures used to implement a vfiler boundary check according to the present invention; and

[0039]FIG. 8 is a flowchart illustrating the sequence of steps involving a multi-stage verification procedure associated with the boundary check of the present invention.

DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT

[0040]FIG. 1 is a schematic block diagram of a computer network <b>100</b> including a plurality of clients <b>110</b> and a file server, such as a network storage appliance, that may be advantageously used with the present invention. The file server or filer <b>200</b> is a computer that provides file service relating to the organization of information on storage devices, such as disks. The clients <b>110</b> may be general-purpose computers configured to execute applications including file system protocols, such as the conventional Common Internet File System (CIFS) and Network File System (NFS) protocols. Moreover, the clients <b>110</b> may interact with the filer <b>200</b> in accordance with a client/server model of information delivery. That is, each client may request the services of the filer, and the filer may return the results of the services requested by the client, by exchanging packets <b>120</b> encapsulating, e.g., the CIFS and NFS protocol formats over the network <b>100</b>. It will be understood to those skilled in the art that the inventive technique described herein may apply to any server capable of providing a service to any client in accordance with various applications executing on the client communicating with server applications on a server.

[0041] The filer <b>200</b> may be coupled to an intermediate network node, such as a router or switch <b>150</b>, over a plurality of physical links <b>180</b>, each of which may comprise, e.g., a gigabit Ethernet link, a 100 base T Ethernet link, a 10 base T Ethernet link or any similar link. The switch <b>150</b> is further coupled to the clients <b>110</b> over network clouds <b>130</b> configured as, e.g., local area networks (LANs) or virtual LANs (VLANs). Alternatively, the filer may be connected directly to one or more clients over a communications link <b>140</b> comprising a point-to-point connection or a shared medium, such as a LAN.

[0042]FIG. 2 is a schematic block diagram of the filer <b>200</b> comprising a processor <b>202</b>, a memory <b>204</b>, a storage adapter <b>206</b> and one or more network adapters <b>208</b> interconnected by a system bus <b>210</b>, e.g., a conventional peripheral computer interconnect (PCI) bus <b>210</b>. The filer also includes a storage operating system <b>300</b> that implements a file system to logically organize the information as a hierarchical structure of directories and files on disks <b>216</b> coupled to the storage adapter <b>206</b>. In the illustrative embodiment described herein, the operating system <b>300</b> is preferably the NetApp® Data ONTAP™ operating system available from Network Appliance, Inc. that implements a Write Anywhere File Layout (WAFL) file system.

[0043] The memory <b>204</b> may be apportioned into various sections, one of which is a buffer pool <b>220</b> organized as a plurality of data buffers <b>222</b> for use by network drivers of the operating system <b>300</b>. Each network driver is assigned a list of buffers <b>222</b> that is used to load incoming data requests received at interfaces <b>218</b> of the network adapter <b>208</b>, as described herein. Other sections of the memory may be organized as storage locations that are addressable by the processor and adapters for storing software program code and data structures associated with the present invention. The processor and adapters may, in turn, comprise processing elements and/or logic circuitry configured to execute the software code and access the data structures. The storage operating system <b>300</b>, portions of which are typically resident in memory and executed by the processing elements, functionally organizes the filer by, inter alia, invoking storage and network operations in support of the services implemented by the filer <b>200</b>. It will be apparent to those skilled in the art that other processing and memory means, including various computer readable media, may be used for storing and executing program instructions pertaining to the inventive technique described herein.

[0044] The network adapter <b>208</b> may comprise a network interface card (NIC) having the mechanical, electrical and signaling circuitry needed to connect the filer <b>200</b> to the switch <b>150</b> over the physical links <b>180</b>. In one embodiment, the physical links and interfaces may be organized as an aggregate or virtual interface (VIF) <b>190</b>. Each NIC may include a single interface <b>218</b> such that, for a 4-link VIF, the filer includes 4 NICs <b>208</b>. Alternatively, each NIC <b>208</b> may include 4 “quad port” interfaces <b>218</b>, each of which is connected to a link <b>180</b> of the VIF <b>190</b>. In another embodiment, the physical links and interfaces may be arranged as a de-aggregate or VLAN. Each interface <b>218</b> may be assigned one or more Internet Protocol (IP) addresses along with one media access control (MAC) address. However, when the physical interfaces <b>218</b> and their associated links <b>180</b> are aggregated as a single virtual interface <b>190</b>, all of the physical interfaces respond to only one MAC address. That is, the physical interfaces <b>218</b> are organized into one virtual “pipe” having one logical interface that is assigned a common MAC address.

[0045] The storage adapter <b>206</b> cooperates with the storage operating system <b>300</b> executing on the filer to access information requested by the client, which information may be stored on any storage media, such as the disks <b>216</b>. The storage adapter includes input/output (I/O) interface circuitry that couples to the disks over an I/O interconnect arrangement, such as a conventional high-performance, Fibre Channel serial link topology. The information is retrieved by the storage adapter and, if necessary, processed by the processor <b>202</b> (or the adapter <b>206</b> itself) prior to being forwarded over the system bus <b>210</b> to the network adapter <b>208</b>, where the information is formatted into a packet <b>120</b> and returned to the client <b>110</b>.

[0046] Storage of information on the filer is preferably implemented as one or more storage “volumes” that comprise a cluster of physical storage disks <b>216</b>, defining an overall logical arrangement of disk space. Each volume is generally associated with its own file system. To facilitate access to the disks <b>216</b>, the storage operating system <b>300</b> implements a file system that logically organizes the information as a hierarchical structure of directories and files on the disks. Each “on-disk” file may be implemented as set of disk blocks configured to store information, such as data, whereas the directory may be implemented as a specially formatted file in which information about other files and directories are stored. As noted, the storage operating system is preferably the Data ONTAP operating system that implements a WAFL file system. However, it is expressly contemplated that any appropriate file system can be used, and as such, where the term “WAFL” is employed, it should be taken broadly to refer to any file system that is otherwise adaptable to the teachings of this invention.

[0047]FIG. 3 is a schematic block diagram of the Data ONTAP operating system <b>300</b> that may be advantageously used with the present invention. The storage operating system comprises a series of software layers, including a media access layer <b>310</b> of network drivers (e.g., a gigabit Ethernet driver). The operating system further includes network protocol layers, such as the IP layer <b>312</b> and its supporting transport mechanisms, the Transport Control Protocol (TCP) layer <b>314</b> and the User Datagram Protocol (UDP) layer <b>316</b>. A file system protocol layer provides multi-protocol data access and, to that end, includes support for the CIFS protocol <b>318</b>, the NFS protocol <b>320</b> and the Hypertext Transfer Protocol (HTTP) protocol <b>322</b>. The storage operating system <b>300</b> also includes a disk storage layer <b>324</b> that implements a disk storage protocol, such as a Redundant Array of Independent Disks (RAID) protocol, and a disk driver layer <b>326</b> that implements a disk access protocol such as, e.g., a Small Computer Systems Interface (SCSI) protocol.

[0048] Bridging the disk software layers with the network and file system protocol layers is a WAFL layer <b>330</b> that preferably implements the WAFL file system. The on-disk format representation of the WAFL file system is block-based using, e.g., 4 kilobyte (kB) blocks and using inodes to describe the files. An inode is a data structure, e.g., a 128-byte structure, which is used to store information, such as meta-data, about a file. The meta-data contained in an inode may include, e.g., ownership of the file, access permission for the file, size of the file, file type, unit of storage associated with the file and location of the file on disk. The WAFL file system uses a file handle, i.e., an identifier that includes an inode number, to retrieve an inode from disk. The WAFL layer <b>330</b> also uses files to store meta-data describing the layout of its file system. These meta-data files include, among others, an inode file.

[0049] Operationally, a request from a client <b>110</b> is forwarded as, e.g., a conventional CIFS or NFS protocol packet <b>120</b> over the computer network <b>100</b> and onto a network adapter <b>208</b> of the filer <b>200</b>. A network driver of the media access layer <b>310</b> cooperates with the network adapter to load the request packet into a data buffer <b>222</b> and marks the buffer with the name of the physical interface <b>218</b> over which the incoming request was received at the filer. Each buffer <b>222</b> includes a header <b>224</b> and a data portion <b>226</b>, with the incoming packet being loaded into the data portion. The contents of the header are maintained by the filer and include (i) the type of buffer, (ii) various flags and (iii) the incoming interface marked by the filer. After being loaded with the incoming packet, the buffer <b>222</b> is essentially “pushed up” the network protocol stack and delivered to an appropriate application which services the requests by, e.g. fetching data stored on disks of the filer.

[0050] Specifically, the network driver <b>310</b> passes the buffer to the network protocol layers <b>312</b>-<b>314</b> and onto the CIFS or NFS layer <b>318</b>, <b>320</b> for additional processing prior to forwarding to the WAFL layer <b>330</b>. The WAFL file system generates operations to load (retrieve) the requested data (and inode) from disk <b>216</b> if it is not resident “in core”, i.e., in the memory <b>204</b>. If the information is not in memory, the WAFL layer <b>330</b> indexes into the inode file using the inode number to access an appropriate entry and retrieve a logical volume block number (VBN). The WAFL layer then passes the logical VBN to the disk storage (RAID) layer <b>324</b>, which maps that logical number to a disk block number and sends the latter to an appropriate driver (e.g., SCSI) of the disk driver layer <b>326</b>.

[0051] The disk driver accesses the disk block number from disk <b>216</b> and loads the requested data block(s) in memory <b>204</b> for processing by the filer. Upon servicing the request, the CIFS or NFS layer <b>318</b>, <b>320</b> allocates another (response) buffer <b>222</b> from the buffer pool <b>220</b> for the fetched data and further associates that response to the initial request. That is, the CIFS or NFS layer marks the response buffer with the physical interface associated with the incoming request.

[0052] As noted, the filer <b>200</b> is configured to provide file service to a plurality of clients <b>110</b> and, as a result, generally returns data responsive to requests issued by the clients. In order to enhance its responsiveness, the filer implements a “fast path” technique that essentially returns a response over the same physical interface <b>218</b> that was used to receive a request from the client. To invoke the fast path technique, the CIFS or NFS layer <b>318</b>, <b>320</b> asserts a fast path flag within the buffer header <b>224</b> and then passes the buffer “down” the protocol stack to the IP layer <b>312</b>, which examines the state of that flag. Assertion of the fast path flag informs the IP layer that it does not have to perform route calculation for this particular response. Accordingly, the interface within the filer targeted to receive the response buffer is the incoming interface <b>218</b> over which the request was received. The buffer is forwarded to that interface and the requested data is then returned to the client <b>110</b> over the network <b>100</b>.

[0053] It should be noted that the software “path” through the storage operating system layers described above needed to perform data storage access for the client request received at the filer may alternatively be implemented in hardware. That is, in an alternate embodiment of the invention, the storage access request data path <b>350</b> may be implemented as logic circuitry embodied within a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). This type of hardware implementation may increase the performance of the file service provided by filer <b>200</b> in response to a file system request packet <b>120</b> issued by client <b>110</b>. Moreover, in another alternate embodiment of the invention, the processing elements of adapters <b>206</b>, <b>208</b> may be configured to offload some or all of the packet processing and storage access operations, respectively, from processor <b>202</b>, to thereby increase the performance of the file service provided by the filer. It is expressly contemplated that the various processes, architectures and procedures described herein can be implemented in hardware, firmware or software.

[0054] As used herein, the term “storage operating system” generally refers to the computer-executable code operable to perform a storage function in a storage system, e.g., that implements file system semantics and manages data access. In this sense, the ONTAP software is an example of such a storage operating system implemented as a microkernel and including the WAFL layer to implement the WAFL file system semantics and manage data access. The storage operating system can also be implemented as an application program operating over a general-purpose operating system, such as UNIX® or Windows NT®, or as a general-purpose operating system with storage applications described herein or with configurable functionality, which is configured for storage applications as described herein.

[0055] In addition, it will be understood to those skilled in the art that the inventive technique described herein may apply to any type of special-purpose (e.g., file serving appliance) or general-purpose computer, including a standalone computer or portion thereof, embodied as or including a storage system. A server may be defined as a computer adapted to provide application service to one or more clients; in this context, a virtual server is an instance of the application service provided to a client. Moreover, the teachings of this invention can be adapted to a variety of storage system architectures including, but not limited to, a network-attached storage environment, a storage area network and disk assembly directly-attached to a client or host computer. The term “storage system” should therefore be taken broadly to include such arrangements in addition to any subsystems configured to perform a storage function and associated with other equipment or systems.

[0056] Vfiler

[0057] The present invention comprises an architecture that provides the ability to create and maintain multiple instances of virtual servers, such as virtual filers (vfilers), within a single server, such as a filer. A vfiler is a logical partitioning of network and storage resources of the filer platform to establish an instance of a multi-protocol server. Each vfiler is maintained and executed entirely independent of other vfilers on the platform. To that end, dedicated filer resources, such as units of storage and network addresses of network interfaces, may be arbitrarily grouped and “hard” partitioned to establish security domains within the filer. Yet common filer resources, such as a storage operating system and a file system, may be shared among the vfilers.

[0058] Specifically, each vfiler is allocated a certain amount, i.e., a subset, of dedicated and distinct units of storage resources, and one or more dedicated and distinct network addresses. Each vfiler is also allowed shared access to the common file system on behalf of its client. Therefore, interpretations of a security object associated with, e.g., a client accessing the common file system may vary among vfilers. To address this, each vfiler is provided a vfiler context data structure (hereinafter “vfiler context”) including, among other things, information pertaining to a unique and distinct security domain of the vfiler to thereby enable controlled access to allocated and shared resources of the vfiler.

[0059] For example, the vfiler context of a first vfiler ensures that users or clients of a first security domain can use a first set of source and destination network addresses when issuing requests to access a first subset of storage resources on the filer. Similarly, the vfiler context of a second vfiler ensures that clients of a second security domain may use a second set of source and destination network addresses to access a second subset of storage resources. Notably, the clients of each security domain are unaware of each other's “presence” on the filer and, further, are unable to access each other's storage resources. In sum, no data flow exists between vfilers.

[0060]FIG. 4 is a schematic diagram of an embodiment of a filer platform <b>400</b> having a plurality of vfilers in accordance with the present invention. Each vfiler may be embodied as a server, e.g., a CIFS server, which is referenced by a logical name, e.g., VF1-VF3. From the perspective of a client, each vfiler is separate and distinct from the other vfilers. Each vfiler VF1-VF3 is configured with one or more Internet Protocol (IP) addresses that may be assigned to one or more network interfaces <b>408</b><i>a</i>-<i>c</i>. In this context, the term network interface refers to an IP addressable interface, including a “physical” NIC and a “soft” NIC, such as a VIF, a VLAN and an emulated LAN (ELAN). Notably, a single NIC can support a plurality of IP addresses and, with such a configuration, multiple vfilers can effectively share a single NIC, if desired.

[0061] Each interface of the filer is further assigned an IPspace identifier (ID) <b>406</b><i>a</i>-<i>c </i>that essentially “binds” the interface to an IPspace. An IPspace refers to a distinct IP address space in which the filer and its storage operating system participate. A single filer can support multiple IPspaces. Each vfiler is associated with an IP address space and, thus, belongs to one IPspace. The IP addresses within each IPspace must be unique. The IPspace is further described in copending and commonly-assigned U.S. Patent Application Serial No. (112056-0023) titled, Technique for Enabling Multiple Virtual Filers on a Single Filer to Participate in Multiple Address Spaces with Overlapping Network Addresses, which is hereby incorporated by reference as though fully set forth herein.

[0062] The units of storage resources allocated to each vfiler include a volume or sub-volume (qtree). A volume (V) <b>410</b> is a unit of storage comprising a file system or hierarchy of directories and files. A qtree, QT<b>1</b>-<b>3</b><b>420</b>, is a special directory similar to a mini-volume (mini-file system) or subdivision of a volume that has the property of being able to identify itself within a file system by, e.g., a qtree identifier (qtreeid) stored within an inode of a file. The vfiler architecture provides efficient utilization and management of these storage resources, including creation, assignment and mapping of the resources to and among the vfilers. For example, a virtual server (such as vfiler) and its associated storage resources (such as qtrees) may be migrated to a server (such as a filer) and consolidated with other virtual servers (vfilers) having similarly named resources. Since the storage resources are allocated on a per-vfiler basis, such server consolidation and storage migration are transparent to a client because there is no change in the way the client refers to its data.

[0063] Encapsulation

[0064] Each instance of a vfiler is described by “external” and “internal” configuration. External configuration describes the resources assigned to a vfiler (e.g., one or more IP addresses and one or more units of storage, such as an entire volume or a qtree on a volume) and capabilities available to a vfiler (e.g., protocols allowed to run on the vfiler). Internal configuration (i.e., internal to the vfiler) controls operation of various protocol modules or “vfiler options” associated with the vfiler. Examples of such options include whether a network information system (NIS) server is to be used with the vfiler and whether a particular protocol, such as NFS, uses TCP or UDP as its underlying transport.

[0065] On-Disk Representation

[0066] The external configuration information described above is preferably stored “on-disk” in a global registry of the physical filer (which is typically stored on the root volume of the filer), whereas the internal configuration is stored in a private registry in the storage assigned to the vfiler. Given the split configuration of a vfiler, all information needed to create a vfiler on a new “head” is typically not available when migrating storage devices, such as disks, belonging to a vfiler from one physical filer to another. Note that a “head” is defined as all parts of a filer excluding disk shelves. The internal configuration is available, but the external information is only available on the old filer.

[0067] In an embodiment of the present invention, the external configuration information can be redundantly stored on the migrated disks of the vfiler. However, this information must be stored in such as fashion that it is not accessible (modifiable) to an administrator of the vfiler. The external configuration is preferably stored in a meta-data portion of all file system units (e.g., volumes) of the migrated disks. When the migrated disks of a disk shelf are attached to the filer platform, the disk software layers of the storage operating system search for the external configuration information in the attached storage units and instantiates those vfilers that are “discovered”. This allows moving of a vfiler simply by removing the disk shelf containing its storage disks from one physical filer head and attaching them into another physical filer head or by storing the external configuration information in encrypted form on data that may be replicated or migrated.

[0068] According to an aspect of the invention, a vfiler is created by the following command line interface (CLI) command of a user interface associated with the operating system:

[0069] vfiler create [xyz][−s IPspace-name][−i IP address(s)][/vol/vol2][/vol/vol3/qt1]

[0070] wherein xyz is the name of the created vfiler, −s IPspace-name is the name of the IPspace to which the vfiler belongs and −i IP address(s) denotes a particular IP address or series of IP addresses of the vfiler. In addition, the notation /vol/vol2 is a first path descriptor to a first unit of storage, whereas the notation /vol/vol3/qt1 is a second path descriptor to a second unit of storage. The default vfiler is vfiler 0 (VF0) that is created at initialization upon booting of the physical filer; VF0 is the only vfiler embodied in the filer if no other vfilers are created. The default VF0 is associated with the physical filer platform to enable access to, e.g., filer resources that are unassigned after all resource assignments have been made for all vfilers on the filer. When no vfilers are defined, VF0 includes all resources of the filer.

[0071] In Core Representation

[0072] In particular, the vfiler create CLI command creates a vfiler context <b>500</b><i>a</i>-<i>c </i>for each vfiler. Note that a vfiler context is created for VF0 at initialization of the filer. FIG. 5 is a schematic block diagram illustrating an in core representation of a vfiler context <b>500</b> containing configuration information or “state” needed to establish an instance of a multi-protocol server. Multiple instances of these contexts provide the basis for the vfiler architecture. The vfiler context <b>500</b> includes fields for holding a name <b>502</b> of the vfiler and a universally unique identifier (UUID <b>504</b>) that is created with the vfiler context. The UUID may comprise, e.g., the current time of day and a medium access control (MAC) address associated with the vfiler. A vfiler list field <b>506</b> contains a list of vfilers on the filer platform and an IPspace indicator (ID) field <b>508</b> holds the IPspace ID of the vfiler.

[0073] Resource Mapping

[0074] According to the vfiler architecture, hardware resources, such as storage and network devices, are not directly assigned to the vfilers. Instead, software objects representing (in full generality) only a portion of the capabilities of these hardware devices are assigned to the vfilers. These software (“soft”) objects correspond only to a “dynamically adjustable” portion of a hardware resource. The advantage of using soft objects for assignment to a vfiler is total flexibility in allocating, adding, moving and removing complete or portions of hardware resources between vfilers on a physical filer. These operations can be accomplished very quickly using, e.g., a simple short-running console command as opposed to a complex, long-running procedure of re-configuring or copying hardware objects between hardware partitioning based virtual servers, such as a VM or data mover.

[0075] Therefore, other fields of the vfiler context structure <b>500</b> hold a list <b>510</b> of virtual filer storage (vfstore) structures (soft objects) and a list <b>512</b> of virtual filer network (vfnet) soft objects. FIG. 6 is a schematic block diagram illustrating soft object data structures that may be advantageously used with the present invention. In particular, the vfstore list <b>510</b> comprises pointers to vfstore soft objects <b>610</b>, each of which has a pointer <b>612</b> that references a path to a unit of storage resource, such as a qtree or volume, allocated to the vfiler. This allows, e.g., a volume consisting of multiple qtrees to be effectively shared between vfilers. A hash table (not shown) is also provided that “maps” each qtree or volume back to a vfiler context <b>500</b> (and thus a vfstore <b>610</b>).

[0076] The vfnet list <b>512</b> comprises pointers to vfnet soft objects <b>620</b>, each of which has a pointer <b>622</b> that references an interface address (ifaddr) data structure <b>640</b> representing an IP address assigned to the vfiler. Each vfnet object <b>620</b> represents a “floating” capability that may be assigned to any network interface, e.g., a NIC, when an IP address is assigned to that NIC. If multiple IP addresses are assigned to the NIC, the capabilities of the NIC are effectively shared between multiple vfnet objects <b>620</b> and, thus, potentially different vfilers. If only a single IP address is associated with an interface (as represented by an interface network (ifnet) data structure <b>630</b>), only one vfnet object <b>620</b>, and therefore only one vfiler, uses the capabilities of the NIC.

[0077] In accordance with another aspect of the invention, resource mapping is defined as the mapping between soft objects that represent assigned resources of a vfiler (e.g., vfstore and vfnet objects) to portions of hardware resources, such as a qtree/volume and an ifnet structure. The vfstore and vfnet soft objects thus provide a level of indirection that represents the dynamically adjustable portions of capabilities of these hardware resources. That is, these soft objects are “linked” to other software objects (data structures) representative of the hardware resources in a manner that enables flexibility when “logically” reassigning those network and storage resources by, e.g., changing pointers of the objects. Such flexibility allows logical establishment of vfiler configuration changes at the file system level, as opposed to physical establishment by, e.g., manually rearranging the network and storage hardware resources.

[0078] For example, an ifnet structure <b>630</b> includes an IP list field <b>632</b> that contains a list of IP addresses assigned to a network interface. The list <b>632</b>, in turn, includes pointers <b>634</b> that reference appropriate ifaddr data structures <b>640</b> associated with those IP addresses. As noted, each vfnet object <b>620</b> may contain a pointer <b>622</b> to an ifaddr structure <b>640</b> (if the corresponding IP address is configured on an ifnet structure <b>630</b>) or may contain a null value (if the address is not configured). Each ifaddr structure <b>640</b> also contains a back link pointer <b>642</b> to the vfiler context <b>500</b> (and therefore to a corresponding vfnet object <b>620</b>).

[0079] Similarly, each vfstore object <b>610</b> has a pointer <b>612</b> to a path of a unit of storage, if the storage resource is online. In the illustrative embodiment, the WAFL file system <b>330</b> maintains information relating to the availability and scope of units of storage, such as qtrees and volumes. System calls are provided to query the file system with a path and, in response, receive a storage identifier tuple (e.g., fsid, qtreeid) that indicates the volume and qtree to which the path belongs.

[0080] Resource mapping in the vfiler architecture further enables efficient network and storage management with respect to, e.g., migration (assignment) of network and storage resources among vfilers. Network management refers to the set of data structures and algorithms that maintain the resource mapping between vfilers and their network resources as dynamic changes are made to the assignment of these resources and other changes on the filer platform. Storage management, on the other hand, refers to the set of data structures and algorithms that maintain the resource mapping between vfilers and their storage resources as dynamic changes are made to the assignment of these resources and other changes on the platform. Assignment changes include the addition, movement and removal of resources between vfilers. Other system changes include the creation of new NICs (VIFs and VLANs, or new devices) or the addition/on-lining/off-lining of storage volumes.

[0081] Network and storage management also includes the tasks performed on networking and storage objects when changes are made to the assignments of resources between vfilers. For example, TCP/IP connections and routing associated with an IP address must be reinitialized when the vfiler assignment of an IP address changes. Similarly, disk input/output operations that are in progress on a qtree or volume must be aborted, and quotas must be reinitialized when the vfiler assignment of a storage unit changes.

[0082] Security

[0083] Another aspect of the present invention is directed to security and the creation of security domains on the filer platform <b>400</b>. The storage operating system <b>300</b> and its WAFL file system <b>330</b> implement the notion of multi-protocol security wherein every file has a form of native security, e.g., UNIX-style or NT (NTFS)-style. The native security style of a file is available from security information contained in the inode of the file. In the case of a NFS file, the UNIX-style security information stored in the inode comprises (i) an owner of file, (ii) a user ID and primary group ID (“security objects”), and (iii) permissions/rights for user and group. For NT-style security file, a pointer in the inode references a security descriptor that comprises similar owner, security object and permissions/rights information.

[0084] A feature of the novel vfiler architecture is that each vfiler is associated with a unique and distinct security domain from the perspective of a client. In addition, each vfiler shares access to a common file system (e.g., the WAFL file system). Accordingly, interpretations of the security object associated with, e.g., a client accessing the common file system may vary among vfilers because each vfiler is associated with its own security domain. To address this, each vfiler context further includes information pertaining to the security domain of the vfiler to thereby enable controlled access to allocated and shared resources of the vfiler. Specifically, each vfiler context <b>500</b> has a pointer to an /etc/passwd,group file <b>516</b> containing a user ID and group ID associated with each user password. Additionally, each vfiler context includes its own set of local Windows users and groups, together with network connections and other mechanisms necessary for authentication in a Windows environment, as described herein.

[0085] Because of the multi-protocol nature of the storage operating system, a situation may arise where an NT user (Windows client) may attempt to access a file having UNIX-style security (or vice versa, where a UNIX user/client may access a file having NT-style security). The vfiler architecture further includes a multi-protocol feature that supports multiple different clients having different types of security, and the ability to map those different client security types to different vfilers of a filer. In particular, the WAFL file system <b>330</b> implements a multi-protocol mapping procedure to determine whether a client can access a requested resource/file. This mapping procedure generally involves the use of a security controller associated with the security style of the resource to perform lookup operations into a security database to resolve the identity of the client/user. The novel vfiler context structure <b>500</b> implements this feature by providing a pointer that references a multi-protocol mapping library file <b>518</b> that enables translation of permission checking attributes from one protocol to another (e.g., NFS to NT security).

[0086] Broadly stated, assume a client forwards an NFS request to the filer <b>400</b> to access a file having NT-style security. The request includes a set of credentials that has an associated UNIX-style user ID. Therefore, the file system <b>330</b> must translate the UNIX user ID to an NT user ID in order to determine the “NT” identity of the user. The file system <b>330</b> looks up the user ID in the /etc/passwd file <b>516</b> to identify a UNIX user name for the user ID and then translates the user name to an NT user name using the mapping library file <b>518</b>. The file system then accesses a controller, e.g., an NT domain controller, to provide an NT-style security identifier (as manifested by a credential) for the NT user name. The domain controller returns the credential to the file system, which compares access rights specified therein with an access control list (ACL) associated with the inode of the requested file. An example of a multi-protocol mapping procedure that may be advantageously used with the present invention is described in U.S. patent application Ser. No. 09/035,234 titled, File Access Control in a Multi-Protocol File Server, by Hitz et al., filed Mar. 3, 1998, which application is hereby incorporated by reference.

[0087] Each vfiler context <b>500</b> further includes a plurality of “module” data structures that includes all information (such as global variables) needed for an instance of a particular protocol or subsystem. For example, a CIFS module data structure <b>520</b> contains all information needed for an instance of the CIFS protocol, including information about contacting a domain controller <b>522</b>, active sessions <b>524</b> for the protocol and various control blocks <b>525</b> associated with the CIFS protocol. The domain controller is a network server that accepts logon requests and initiates their authentication. Information pertaining to a security domain <b>526</b> is also provided to enable NT-type security for a CIFS request. The security information includes a security identifier comprising a domain portion and a relative ID (RID) portion, the latter RID being similar to the user ID of UNIX security. In the case of Windows domain security, the security information also includes a trust relationship with the domain controller. The trust relationship signifies the ability of a vfiler to “trust” the domain controller to authenticate a user on behalf of the vfiler. Each CIFS module <b>520</b> also contains a process ID (PID <b>528</b>) of the CIFS authentication process that enables the CIFS layer to send an authentication request to the correct CIFS authentication process.

[0088] There is a similar “per-module” data structure for each of the protocols and subsystems associated with a vfiler including, but not limited to, the NFS protocol <b>530</b>, Remote SHell (RSH) protocol <b>540</b>, Telnet protocol <b>550</b>, NIS subsystem <b>560</b>, domain name service (DNS) subsystem <b>570</b> and registry <b>580</b>. The NIS subsystem or “yellow pages” is a service locator for the NFS protocol that is implemented as a distributed database storing security information, such user and group IDs associated with each user password. The NIS subsystem module <b>560</b> includes information for contacting a NIS controller when access to the distributed security database is required (using, e.g., the /etc/passwd,group information stored in file <b>516</b>). The DNS subsystem facilitates resolution of a DNS name to a corresponding IP address. The registry is a repository for configuration information pertaining to the hardware, software and users of the filer (and each vfiler).

[0089] Boundary Check

[0090] Yet another aspect of the present invention relates to a vfiler boundary check performed by the file system (i.e., WAFL layer <b>330</b>) of the storage operating system <b>300</b> to verify that a requesting vfiler is allowed to access certain storage resources on the filer platform. The vfiler boundary check is based on information, such as the unit of storage (qtree or volume) associated with the file, acquired from an inode of a requested file. For every request to access a unit of storage, a boundary check is performed using this information to determine whether the requesting vfiler is authorized to access the storage resource. If the check reveals that the vfiler is not authorized to access the requested storage resource, the request is immediately denied. Otherwise, the request is allowed and the WAFL file system generates operations to process the request.

[0091] Assume a plurality of NFS clients U1-U3 access a common NFS server. Each NFS client can “see” the set of resources exported by the NFS server. Accordingly, each client can access substantially all resources of the server. In contrast, if the NFS server is configured as filer <b>400</b> (FIG. 4), that server is essentially “divided into” (embodied as) virtual servers VF0-VF3. Each vfiler has its own vfiler context and security domain. Assume further that client U1 is allowed to access vfiler VF1's resources, client U2 is allowed to access VF2's resources and client U3 is allowed to access VF3's resources. U1 will fail the novel boundary checks performed by the file system if it attempts to access VF2's resources. The “logical” boundary checks enforce security (access to shares) within the vfiler domain for all clients, including “hackers” attempting to “spoof” NFS handles. The tools used by the hackers can be used to effectively access any inode on a server, even if that storage is not exported to clients. Therefore, another security aspect of the vfiler architecture involves the use of boundary checks (and their associated data structures) for determining access to storage resources on the physical filer.

[0092]FIG. 7 is a schematic block diagram illustrating the various data structures used to implement the vfiler boundary check. A first data structure, e.g., fsid hash table <b>700</b>, has a plurality of entries <b>710</b>, each associated with a vfiler and accessed by a volume (file system) identifier (fsid) functioning as a key into the table. The fsid is assigned to a volume when the volume is created. Each vfiler entry of the fsid table denotes a vfiler, e.g., VF1, VF2 or VF3, which explicitly (completely) owns the volume identified by the fsid. Using an fsid retrieved from an appropriate inode, a determination can be made whether a particular vfiler completely owns a volume associated with the fsid. A second qtree hash table <b>750</b> has a plurality of entries <b>760</b>, each associated with a vfiler and accessed by a key consisting of an fsid and a qtreeid, the latter of which is also retrieved from the inode. Each vfiler entry of the qtree table denotes a vfiler that owns the qtree identified by the qtreeid. Using the fsid and qtreeid, a determination can thus be made as to whether the vfiler completely owns the qtree of a particular volume (file system).

[0093] The vfiler boundary check is preferably associated with a multi-stage verification procedure for accessing storage resources of the filer. FIG. 8 is a flowchart illustrating the sequence of steps involving the multi-stage verification procedure of the present invention. The sequence starts at Step <b>800</b> and proceeds to Step <b>802</b> where an incoming request (such as NFS, CIFS, HTTP or Telnet packet) is received at a network interface <b>408</b> of the filer and, in Step <b>804</b>, the request is thereafter directed to the proper vfiler based on the destination IP address of the request and the IPspace ID of the interface. For example, assume a driver of the media access layer <b>310</b> receives a CIFS request to access a file having a particular file handle. As noted, the network interface is associated with an IPspace. The network driver passes the request to the IP layer <b>312</b> where the destination IP address of the request and the IPspace ID <b>406</b> are compared with configuration information stored in an IPspace database to select a vfiler context, e.g., virtual filer <b>2</b> (VF2), that owns the request. As a result, a vfiler context <b>500</b><i>b </i>for VF2 is associated with the request. Selection of a vfiler context for processing an incoming request is described more fully in the copending patent application, Technique for Enabling Multiple Virtual Filers on a Single Filer to Participate in Multiple Address Spaces with Overlapping Network Addresses.

[0094] Once the incoming request is associated with a vfiler context, the IP layer <b>312</b> issues a system call to set the vfiler context <b>500</b> for the current process executing on the filer (Step <b>806</b>). Internal to the storage operating system is the notion of a process or thread of control executing on the filer. A process block data structure represents the context of that executing process thread. The process block structure includes the notion of a thread running in a vfiler context. To that end, the process block data structure includes a pointer referencing a current vfiler context executing on the filer. If no vfilers are created/defined on the filer, the processes run in the context of the default vfiler VF0.

[0095] In Step <b>808</b>, the IP layer code <b>312</b> passes the request to the appropriate transport protocol layer (e.g., TCP), which determines that the request is destined for a particular port, e.g., the CIFS layer. That is, the TCP layer code <b>314</b> examines its protocol control block (PCB) tables to determine if there is a “socket” open for a port number included in the request. The port number is used to identify a particular protocol server of the file system protocol layer, e.g., the CIFS layer protocol. The PCB tables are qualified by vfiler and IPspace ID to thereby enable the TCP layer <b>314</b> to determine whether the current vfiler context has an open socket. If so, that TCP layer calls into a NetBIOS over TCP (NBT) layer (shown at <b>315</b> of FIG. 3) that performs framing for the CIFS protocol. Once the NBT layer <b>315</b> has a full request, it calls into the CIFS protocol layer <b>318</b>.

[0096] In Step <b>810</b> the protocol server (CIFS code) executes in the context of the current vfiler context and, in particular, its CIFS module. When a variable is referenced, the appropriate variable is retrieved from the CIFS module <b>520</b> of the current vfiler context <b>500</b>. For example, when executing code in the CIFS layer that specifies, e.g., contacting a domain controller, the code refers to the per-module instance of the CIFS protocol within the current vfiler context to acquire the domain controller contact information <b>522</b>. As noted, all state associated with a vfiler is stored in these per-module data structures. Also, when the vfiler initializes, a set of initialization routines are executed to allocate memory locations, set variables to known values and create processes with the appropriate vfiler ID.

[0097] The CIFS protocol determines the type of access (read) and the particular file (file handle) associated with the request. In Step <b>812</b>, the CIFS protocol server formats a message (WAFL message) associated with the request and passes the message to the WAFL file system. The WAFL message is the mechanism used to forward requests to the WAFL layer <b>330</b> for processing in accordance with certain functions. A field of the WAFL message contains an identification of the current vfiler context. The WAFL file system uses that vfiler context for functions such as replies to requests. Specifically, the WAFL message includes a vfiler pointer that sets the vfiler context for subsequent processing by the WAFL layer code. All code relevant to the “virtualized” context, e.g., code needed to execute protocols or management functions, are “aware” of the current vfiler context they are operating within and what capabilities they have based on that current context.

[0098] If the requested file is not in memory, the WAFL layer uses the file handle to load an inode for the file in core. The file handle is a reference to the inode data structure that is used internally within the file system. The file handle generally consists of a plurality of components including a file ID (inode number). In Step <b>814</b>, the WAFL layer code derives the fsid and qtreeid from the inode for the requested file and executes the multistage verification procedure associated with the novel boundary check prior to processing (servicing) the request.

[0099] Specifically in a first stage of the verification procedure, the fsid is used as an index into the fsid table <b>700</b> (Step <b>816</b>) to determine whether the requesting vfiler (VF2) explicitly “owns” an entire unit of storage, such as the volume identified by the fsid (Step <b>818</b>). If so, VF2 can access the storage resource in Step <b>820</b>. If not, then a second stage of the procedure determines whether the volume is completely owned by another vfiler (Step <b>822</b>). If so, the request is immediately denied in Step <b>824</b> and the procedure ends in Step <b>840</b>. If the volume is not explicitly owned by another vfiler, then a third stage of the procedure uses the fsid and qtreeid as an index into the qtree table <b>750</b> (Step <b>826</b>) to determine if VF2 owns a portion of the volume, such as a qtree identified by the qtreeid (Step <b>828</b>). If so, VF2 can access the storage resource in Step <b>830</b>. If not, the request is immediately denied in Step <b>832</b> and the procedure ends in Step <b>840</b>.

[0100] Assuming the boundary checks of the verification procedure are satisfied, the WAFL layer <b>330</b> services the request in Step <b>834</b> and calls back into the CIFS layer <b>318</b>. As noted, the WAFL message generated by the CIFS layer includes the current vfiler context. The CIFS protocol then generates a response in Step <b>836</b> and forwards it down the network protocol layers and over the network to the client issuing the request in Step <b>838</b>. The sequence then ends in Step <b>840</b>.

[0101] Assume now that the incoming request is an authentication request. Authentication occurs at the CIFS layer <b>318</b>. Assume the CIFS protocol determines it needs to contact an external server, e.g., a Kerberos server, to authenticate. Accordingly, a CIFS authentication process is created (spawned) in the context of a vfiler (context). The CIFS layer sends a message to a CIFS authentication process for the current vfiler. As noted, each CIFS module <b>520</b> contains the PID <b>528</b> of the CIFS authentication process; this enables the CIFS layer to send the message to the correct CIFS authentication process. Once the CIFS authentication process contacts the domain controller and receives, e.g., an acknowledgement that the request authenticates, the authentication process generates a response and sends it down the network protocol layers.

[0102] In accordance with the inventive architecture, all vfilers may “share” the same process for some operating system function, e.g., a WAFL thread; the WAFL thread sets its vfiler based on an indicator in the WAFL message. In other cases, a separate process is create for each instance of the vfiler, particularly for possible “blocking” operations, such as waiting to contact a domain controller. For these latter cases, it is not desirable to “hold up” other vfilers during the time it takes to contact the domain controller.

[0103] In sum, the novel vfiler architecture facilitates both consolidation of virtual servers and their respective data applications on a single filer, as well as encapsulation of all server resources. Server consolidation is achieved through the creation of vfilers, each of which is associated with a security domain. The security domains are completely disjoint, thereby providing separate and independent vfilers within the same filer platform. This aspect of the invention is particularly useful in the case of a storage service provider, wherein the data applications of multiple client organizations are hosted on the filer. Each client organization can access only its own vfiler(s) and is entirely unaware that it is sharing the same physical filer with other client organizations. The novel architecture thus obviates the need to dedicate a filer for each client organization.

[0104] Moreover, the vfiler architecture provides ease of administration with respect to migration of storage resources because the vfiler encapsulates all resources associated with a server. That is, storage migration between and among filers is transparent to clients since the storage resources are allocated on a per-vfiler basis. This obviates the need for a client to change the way (e.g., path descriptor) it refers to its data when the vfiler is moved or copied to another physical filer. In addition, the cost of hardware resources and software needed to provide instances of the vfilers is reduced with respect to separate hardware platforms.

[0105] As noted, prior systems are configured to run multiple instances of a server. For example, the virtual machine (VM) operating system from IBM Corporation enables execution of multiple instances of servers on one hardware platform. However, each instance of a VM has its own file system, as well as its own network and storage resources. That is, the network and storage resources of the platform are apportioned and pre-assigned to instances of VMs embodied on the platform. In contrast, the vfiler architecture employs one file system shared by all vfilers with the flexibility to “logically” reassign network and storage resources by, e.g., changing data structures described herein. Therefore, changes to the vfiler configuration are logically instituted at the file system level as opposed to physically rearranging network and storage resources, or reformatting file systems.

[0106] Another prior art system is an open source Windows server, e.g., Samba, running on a UNIX operating system platform. The Samba architecture may be implemented at the application layer to provide multiple instances of NT servers running on the UNIX platform. In order to “tie” a server instance to a physical network interface and a security domain to thereby ensure, e.g., security and diversity of security domains among server instances, such an implementation would be forced to modify the networking infrastructure of the underlying UNIX operating system. In contrast, the boundary checking mechanism of the novel vfiler architecture is a function of the networking code of the storage operating system used to configure IP addresses for each vfiler instance. The ability to have an independent security domain (per access protocol) is a first-class property of the vfiler architecture.

[0107] In addition, the Celerra architecture available from EMC Corporation utilizes the notion of a data mover that corresponds to an instance of a filer. The data mover “front ends” a Symmetrix storage device having storage resources that can be logically apportioned and assigned to various other data movers. Each data mover has its own set of networking hardware. However, each data mover further includes its own processor running its own copy of the operating system. This is equivalent to “racking together” a plurality of independent “physical” server platforms. In contrast, the vfiler architecture can support many “logical” instances of vfilers within a single filer platform, thereby increasing the scalability of the architecture. Moreover, the novel architecture employs one file system that is shared by all virtual filers and has the flexibility to logically reassign storage resources at the file system level. By sharing common physical filer attributes, such as processor, memory, network interface and operating system resources, the vfiler architecture approach is more cost effective than the prior solutions.

[0108] Specifically, vfiler architecture facilitates sharing of resources, particularly for stand-by resources needed for, e.g., fault failover situations. Prior systems preclude such resource sharing because the stand-by resources may not share the same address space, e.g., are not attached to the same physical machines. As a result, the resources cannot be dynamically reconfigured on the platform. In contrast, the novel vfiler architecture is capable of maintaining a shared “spare” pool of networking and storage resources (such as NICs and disk drives) that can be dynamically allocated to a filer. In this context, dynamic allocation refers to “on-the-fly” logical assignment of resources, as opposed to physical relocation of devices/hardware among various platforms.

[0109] While there has been shown and described an illustrative embodiment of an architecture that provides the ability to create and maintain multiple instances of vfilers within a filer, it is to be understood that various other adaptations and modifications may be made within the spirit and scope of the invention. For example, in an alternate embodiment, the novel vfiler architecture does not preclude the sharing of a security domain by multiple vfilers. That is, each vfiler may have its own volume and qtree resources, but still be able to share information (e.g., within a NIS domain) with other vfilers. Furthermore, although different vfilers are configured with their own units of storage (e.g., volumes), at the discretion of a physical filer administrator, a particular vfiler (e.g., the default vfiler) could be allowed access to any storage on the platform that is associated with any other vfiler.

[0110] The foregoing description has been directed to specific embodiments of this invention. It will be apparent, however, that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their advantages. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the invention.