32 results about "Global Namespace" patented technology

The disclosed embodiments disclose techniques for managing a global namespace for a distributed filesystem. Two or more cloud controllers collectively manage distributed filesystem data that is stored in a cloud storage system; the cloud controllers ensure data consistency for the stored data, and each cloud controller caches portions of the distributed filesystem. Furthermore, a global namespace for the distributed filesystem is also split across these cloud controllers, with each cloud controller “owning” (e.g., managing write accesses for) a distinct portion of the global namespace and maintaining a set of namespace mappings that indicate which portion of the namespace is assigned to each cloud controller. During operation, an initial cloud controller receives a request from a client system to access a target file in the distributed system. This initial cloud controller uses the namespace mappings for the global namespace to determine a preferred cloud controller that will handle the request.

In a switched file system, a file switching device is logically positioned between clients and file servers and communicates with the clients and the file servers using standard network file protocols. The file switching device appears as a server to the client devices and as a client to the file servers. The file switching device aggregates storage from multiple file servers into a global filesystem and presents a global namespace to the client devices. The file switching device typically supports a “native” mode for integrating legacy files into the global namespace and an “extended” mode for actively managing files across one or more file servers. Typically, native-mode files may be accessed directly or indirectly via the file switching device, while extended-mode files may be accessed only through the file switching device. The file switching device may manage file storage using various types of rules, e.g., for managing multiple storage tiers or for applying different types of encoding schemes to files. Rules may be applied to pre-existing files.

In a switched file system, a file switching device is logically positioned between clients and file servers and communicates with the clients and the file servers using standard network file protocols. The file switching device appears as a server to the client devices and as a client to the file servers. The file switching device aggregates storage from multiple file servers into a global filesystem and presents a global namespace to the client devices. The file switching device typically supports a “native” mode for integrating legacy files into the global namespace and an “extended” mode for actively managing files across one or more file servers. Typically, native-mode files may be accessed directly or indirectly via the file switching device, while extended-mode files may be accessed only through the file switching device. The file switching device may manage file storage using various types of rules, e.g., for managing multiple storage tiers or for applying different types of encoding schemes to files. Rules may be applied to pre-existing files.

Client computers, a namespace server, and file servers are linked in a data network so that the namespace server provides the clients with NFS or CIFS access to a virtual file system including files stored in the file servers, and also provides migration of files between the file servers in a fashion transparent to the client access using NFS or CIFS. The client computers and storage arrays storing the file data are also linked in a storage area network so that the clients have high speed block access to the file data using a file mapping protocol. The namespace server redirects a metadata access request in the file mapping protocol from a client to the appropriate file server when the file is not being migrated, and otherwise denies the metadata access request when the file is being migrated so that the client reverts to NFS or CIFS access.

Embodiments relate to forwarding of packets in link aggregation environments. A method for forwarding a packet through an extended switch including a first port extender and a second port extender directly or indirectly communicatively coupled to respectively a first interface and a second interface of a controlling bridge includes, associating a first port extender interface of the first port extender with a global namespace or an interface-specific namespace. The method further includes receiving a packet through the first port extender interface, marking the received packet with an indication of the namespace configuration of the first port extender interface, processing the marked packet in the controlling bridge based at least in part upon the indication, and transmitting the processed packet out of the controlling bridge.

A global namespace (GNS) is constructed across heterogeneous network-attached storage (NAS) devices by organizing metadata servers into a cluster layer having cluster nodes and a consistent hashing overlay layer having overlay nodes. The global namespace is distributed based on workload at the cluster and overlay nodes, and a portion of the GNS namespace may be migrated from one layer to the other. Cluster nodes may be added to the cluster layer, overlay nodes may be added to the consistent hashing overlay layer. Further, a cluster node may become an overlay node or an overlay node may become a cluster node. To access the global namespace, a request for namespace metadata managed by a cluster node is serviced by the cluster node, but if the requested namespace metadata have been migrated to the consistent hashing overlay layer, the cluster node will forward the request to the responsible overlay node for servicing.

Inserting a file virtualization appliance into a storage network involves configuring a global namespace of a virtualization appliance to match a global namespace exported by a distributed filesystem (DFS) server and updating the distributed filesystem server to redirect client requests associated with the global namespace to the virtualization appliance. Removing the file virtualization appliance involves sending a global namespace from the virtualization appliance to the distributed filesystem server and configuring the virtualization appliance to not respond to any new client connection requests received by the virtualization appliance.

A system and method for data protection in a logical namespace of a storage system environment is provided. An integrated management framework implements a data protection technique that monitors failures in the logical namespace at a managed data object granularity, e.g., a share. In the event of a failure to the data object, e.g., a primary share, the data protection technique enables automatic failover for a link point to the object (primary share) that is protected by a backup copy of the data object, e.g., a secondary share. That is, the data protection technique enables failover from the primary share to a secondary share and corresponding linking of the secondary share to the link point in the logical namespace.

A DHT-based global namespace (GNS) is constructed for a network system that includes network attached storage (NAS) devices, including at least one DHT-NAS device (a NAS device having DHT Functionalities) and at least one Existing-NAS device (a NAS device lacking DHT Functionalities). In a DHT Overlay Construction Phase, the DHT-NAS devices construct a DHT overlay. In an Initial Phase, the GNS is created above share folders in the Existing-NAS devices, with mapping of the share folders in the Existing-NAS devices to GNS paths distributed to a key lookup table in the DHT-NAS devices. Each mapping in the key lookup table includes a key, a GNS path, NAS type, IP address of the NAS, and the path within the NAS Share. There is no central GNS mapping table. In a Discovery Phase, the DHT-NAS devices discover the Existing-NAS devices to construct the GNS under the share folders. In a Working Phase, the DHT-NAS devices service GNS requests.

A system and techniques are described for creating member private data in a global namespace. According to one aspect, first data that is associated with a key is stored in a repository shared by multiple members. After the first data has been stored, second data that is associated with the key is stored without overwriting the first data. Mapping data is stored. The mapping data maps the key, relative to a first member, to a first data structure that stores the first data. The mapping data also maps the key, relative to a second member, to a second data structure that stores the second data. Based on the mapping data, the first member is allowed to access the first data and not the said second data. Based on the mapping data, the second member is allowed to access the second data and not the first data. The first data and the second data may include key values and subtrees of child keys.

The invention provides an intelligent data service method based on a distributed system. A master node of the distributed system is used for managing global file namespace; and in processes of writing files into the distributed system and reading files from the distributed system, the master node of the distributed system is used for analyzing and processing requests of clients, selecting specific data preprocessing programs, distributing the programs to slave nodes of the distributed system for subsequent data preprocessing and transmission. According to the intelligent data service method based on the distributed system, prior distributed system storage space can be clustered rapidly in data intensive application environments; computing resources of the distributed system are fully used, so that data services can be provided intelligently according to requests of external computing devices; and part of data processing loads are further transferred from external computing devices to the distributed system, and accordingly, bandwidth requirements for providing data services for external computing devices are reduced.

A hierarchical multi-level heterogeneous cluster data system having processing nodes at each of a plurality of cluster levels configured for different data tiers having different availability, accessibility and protection requirements. Each cluster level comprises groups of processing nodes arranged into a plurality of failover domains of interconnected nodes that exchange heartbeat signals to indicate that the nodes are alive and functioning. A master node of each failover domain is connected to a master node of a parent failover domain for exchanging heartbeat signals to detect failures of nodes at lower cluster levels. Upon a network partition, the nodes of the failover domain may be merged into another failover domain at the same or a higher cluster level to continue providing data services. The cluster has a global namespace across all cluster levels, so that nodes that are moved to different failover domains can be accessed using the same pathname.

Methods and systems for processing computer code modules in order to avoid polluting the global namespace. According to one embodiment, the system or method comprises a server that receives a request for an additional computer code module to be added to the namespace. Prior to delivering the module, the server processes the module by identifying all references to global symbols that are not to be explicitly exported to a global scope and moving the identified symbols to a synthetic namespace prior. The server further wraps the processed module in a function that receives the synthetic global scope as a parameter, and delivers the wrapped module to the requesting namespace.

The invention discloses a DFS-oriented client persistent caching method and system in a global namespace, and belongs to the field of large-scale distributed systems, and the method comprises the steps that a metadata server maintains a view of a global directory tree, all clients share the view, and all the clients can access any file through the view; the client identifies a file needing to be prefetched according to the cache prefetching rule, and migrates the file from the object storage server to the local for persistent caching; when the data volume of the local cache of the client exceeds a cache threshold, the data locally cached by the client is replaced; when the client performs file operation, if the to-be-operated file is cached to the local of the client and the client has thecorresponding operation authority, the locally cached file is directly accessed and the operation is finished; otherwise, the file is remotely accessed in the object storage server through the network and the operation is finished. According to the invention, the data management of the distributed file system can be simplified, and the network resource overhead is reduced.

A method for writing data to a storage pool. The method includes receiving a virtual identifier (ID) and an offset for an object, extracting a node identifier (ID) that identifies a first storage server in the storage pool from the virtual ID, obtaining an object layout (OL) for the object from the first storage server, hashing an object ID and an offset ID to obtain a hashed value, where the virtual ID comprises the object ID and where the offset ID is generated from the offset, identifying a second storage server in the storage pool using a global namespace layout (GL), the OL, and the hashed value, and issuing a write request to write data to the object in the second storage server, where the write request comprises the object ID and the offset.