Namespace server using referral protocols

• US 20070055703A1
• Filed: 09/07/2005
• Published: 03/08/2007
• Est. Priority Date: 09/07/2005
• Status: Abandoned Application

• Current Assignee: EMC Corporation (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Faibish, Sorin, Jiang, Xiaoye, Fridella, Stephen, Zimran, Eyal, Gupta, Uday, Wurzl, Mario, Stacey, Christopher
• Application Number:
  US11/221,011
• Publication Number:
  US 20070055703A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/166 File name conversion
• CPC Class Codes: G06F 16/1827 Management specifically adapted to NAS management of storage area networks [SAN] G06F3/067
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

A namespace server translates client requests for access to files referenced by pathnames in a client-server namespace into requests for access to files referenced by pathnames in a NAS network namespace. The namespace server also translates between different file access protocols. If a client supports redirection and is requesting access to a file in a file server that supports the client'"'"'s redirection, then the namespace server may redirect the client to the NAS network pathname of the file. Otherwise, the namespace server forwards a translated client request to the file server, and returns a reply from the file server to the client. A file server may redirect a redirection-capable client'"'"'s access back to the namespace server for access to a share, directory, or file that is offline for migration, or for a deletion or name change that would require a change in translation information in the namespace server.

Claims

1. A multi-protocol namespace server for providing a unified client-server network namespace to clients using different file access protocols to access files in different file servers in a network attached storage (NAS) network namespace, some of the clients using file access protocols that support redirection and others of the clients using file access protocols that do not support redirection, and some of the file servers supporting file access protocols that are not supported by others of the file servers, said multi-protocol namespace server comprising:

memory for storing translation information for translating pathnames in the client-server network namespace to respective translated pathnames in the NAS network namespace and for storing protocol information defining file access protocols for accessing files at the respective translated pathnames in the NAS network namespace, and

at least one processor coupled to the memory for accessing the translation information and the protocol information, said at least one processor being programmed for receiving requests from the clients for access to files referenced by pathnames in the client-server network namespace and translating the pathnames in the client-server network namespace to respective translated pathnames in the NAS network namespace, and for responding to some of the requests from said some of the clients by returning redirection replies to said some of the clients, the redirection replies including translated pathnames in the NAS network namespace, and for responding to the requests from said others of the clients by forwarding translated requests to the file servers, the translated requests including translated pathnames in the NAS network namespace, and for translating and forwarding a request of a client supporting redirection for access to a file upon determining that the file to be accessed by the client supporting redirection is stored in a file server that does not support redirection from the client supporting redirection.

2. The namespace server as claimed in claim 1, wherein said at least one processor is programmed to forward a translated request for file access of the client supporting redirection upon determining that the client supporting redirection is requesting access to a virtual file comprised of more than one virtual file component.

3. The namespace server as claimed in claim 1, wherein said at least one processor is programmed to forward a translated request for file access of the client supporting redirection upon determining that the file to be accessed by the client supporting redirection is stored in a file server that does not support redirection from the client supporting redirection using any file access protocol used by the client supporting redirection.

4. The namespace server as claimed in claim 1, wherein said at least one processor is programmed to forward a translated request for file access of the client supporting redirection upon determining that the client supporting redirection is requesting a deletion or name change of a file in one of the file servers and the deletion or name change of the file in said one of the file servers would require a change in the translation information in said memory.

5. The namespace server as claimed in claim 1, wherein said at least one processor is programmed to forward a translated request for file access of the client supporting redirection upon determining that the client supporting redirection is requesting read-write access to a file having a plurality of copies maintained by the namespace server.

6. The namespace server as claimed in claim 1, wherein said at least one processor is programmed with a Hypertext Transfer Protocol (HTTP) or Extensible Markup Language (XML) interface to the translation information for permitting an installable redirection agent for a client linked to the namespace server to access the translation information.

7. A data processing system comprising:

a namespace server;

at least one redirection capable client linked to the namespace server for transmission of file access requests from said at least one redirection capable client to the namespace server and return of redirection replies from the namespace server to said at least one redirection capable client; and

at least one file server in a network attached storage (NAS) network linked to the namespace server for receipt of forwarded file access requests from the narnespace server and linked to said at least one redirection capable client for receipt of redirected file access requests from said at least one redirection capable client;

wherein the namespace server is programmed for responding to a file access request from said at least one redirection capable client by translating a client-server network pathname in the file access request from said at least one redirection capable client into a NAS network pathname of a physical share in said at least one file server, and returning to said at least one redirection capable client a redirection reply specifying the NAS network pathname of the physical share in said at least one file server; and

said at least one redirection capable client is programmed for responding to the redirection reply by redirecting the file access request to the NAS network pathname of the physical share in said at least one file server, and subsequently sending file access requests for access to the physical share in said at least one file server directly to said at least one file server without redirection from the namespace server; and

wherein said at least one file server is programmed for returning a redirection reply to said at least one redirection capable client in response to an access request from said at least one redirection capable client requesting access to a share, directory, or file that is offline for migration or for which said at least one redirection capable client is requesting a kind of access for which said at least one redirection capable client does not have access permission; and

wherein said at least one redirection capable client is programmed for responding to the redirection reply from said at least one file server by redirecting access to the namespace server.

8. The data processing system as claimed in claim 7, wherein the namespace server is programmed for responding to a redirected access request from said at least one redirection capable client requesting access to a share, directory, or file that is offline for migration by directing access to a target of the migration.

9. The data processing system as claimed in claim 7, wherein the namespace server is programmed for responding to a redirected request from said at least one redirection capable client requesting a kind of access for which said at least one redirection capable client does not have access permission by requesting said at least one file server to perform the kind of access for which said at least one redirection capable client does not have access permission.

10. The data processing system as claimed in claim 7, wherein said at least one file server is programmed so that said at least one redirection capable client does not have access permission to delete or rename a share, directory, or file for which the deletion or renaming would require a change in translation information stored in the namespace server for translating client-server network pathnames into NAS network pathnames;

and wherein the namespace server is programmed for responding to a redirected request from said at least one redirection capable client requesting a deletion or renaming of a share, directory or file for which the deletion or renaming would require a change in translation information stored in the namespace server for translating client-server network pathnames into NAS network pathnames by requesting said at least one file server to perform the deletion or renaming of the share, directory or file for which the deletion or renaming would require a change in translation information stored in the namespace server for translating client-server network pathnames into NAS network pathnames.

11. The data processing system as claimed in claim 7, wherein said namespace server and said at least one redirection capable client are linked together in a client-server network, and said namespace server and said at least one redirection capable client and said at least one file server are linked together in a backend NAS network separate from the client-server network.

12. The data processing system as claimed in claim 7, wherein said namespace server is programmed for forwarding a translated request for file access from said at least one of the clients to said at least one file server upon determining that said at least one of the clients is requesting access to a virtual file component in said at least one file server.

13. The data processing system as claimed in claim 7, wherein said namespace server is programmed for forwarding a translated request for file access from said at least one of the clients to another file server upon determining that said at least one of the clients is requesting access to a file in said another file server and determining that said another file server does not support redirection from said at least one of the clients.

14. A method of request redirection in a data processing system including a namespace server, at least one redirection capable client linked to the namespace server for transmission of file access requests from said at least one redirection capable client to the namespace server and return of redirection replies from the namespace server to said at least one redirection capable client, and at least one file server in a network attached storage (NAS) network linked to the namespace server for receipt of forwarded file access requests from the namespace server and for receipt of redirected file access requests from said at least one redirection capable client, said method comprising the steps of:

the namespace server responding to a file access request from said at least one redirection capable client by translating a client-server network pathname in said file access request from said at least one redirection capable client into a NAS network pathname of a physical share in said at least one file server, and returning to said at least one redirection capable client a redirection reply specifying the NAS network pathname of the physical share in said at least one file server;

said at least one redirection capable client responding to the redirection reply by redirecting the file access request to the NAS network pathname of the physical share in said at least one file server, and subsequently sending file access requests for access to the physical share in said at least one file server directly to said at least one file server without redirection from the namespace server;

said at least one file server returning a redirection reply to said at least one redirection capable client in response to an access request from said at least one redirection capable client requesting access to a share, directory, or file that is offline for migration or for which said at least one redirection capable client is requesting a kind of access for which said at least one redirection capable client does not have access permission; and

said at least one redirection capable client responding to the redirection reply from said at least one file server by redirecting access back to the namespace server.

15. The method as claimed in claim 14, which includes the namespace server responding to a redirected access request from said at least one redirection capable client requesting access to a share, directory, or file that is offline for migration by directing access to a target of the migration.

16. The method as claimed in claim 14, which includes the namespace server responding to a redirected request from said at least one redirection capable client requesting a kind of access for which said at least one redirection capable client does not have access permission by requesting said at least one file server to perform the kind of access for which said at least one redirection capable client does not have access permission.

17. The method as claimed in claim 14, which includes the namespace server responding to a redirected request from said at least one redirection capable client requesting a deletion or renaming of a share, directory or file for which the deletion or renaming would require a change in translation information stored in the namespace server for translating client-server network pathnames into NAS network pathnames by requesting said at least one file server to perform the deletion or renaming of the share, directory or file for which the deletion or renaming would require a change in translation information stored in the namespace server for translating client-server network pathnames into NAS network pathnames.

18. The method as claimed in claim 14, which includes the namespace server translating and forwarding a request for file access of said at least one redirection capable client upon determining that said at least one redirection capable client is requesting access to a virtual file comprised of more than one virtual file component.

19. The method as claimed in claim 14, which includes the namespace server translating and forwarding a request from said at least one redirection capable client for access to a file in another file server upon determining that said another file server does not support redirection from said at least one of the clients.

20. The method as claimed in claim 14, which includes the namespace server translating and forwarding a request for file access of said at least one redirection capable client to said at least one file server upon determining that said at least one redirection capable client is requesting read-write access to a file having a plurality of copies maintained by the namespace server.