Abstract: In some examples, a plurality of nodes may each host a respective logical database (LDB) that includes database data that references external resources stored in a storage system. Further, each node may maintain, for each external resource referenced by the respective LDB on that node, a reference count of a number of references in the respective LDB to each external resource and a timestamp associated with the reference count. In response to addition of a reference to a particular external resource in a particular LDB, a node that hosts the particular LDB may be programmed to increment the reference count and update the timestamp for the particular external resource. Similarly, in response to removal of the reference to the particular external resource in the particular LDB, the node hosting the particular LDB is programmed to decrement the reference count and update the timestamp for the particular external resource.

Abstract: In a namespace distributed across storage devices, collisions of objects stored in the namespace can occur. To manage collisions, first, a collision flag is provided in system metadata of the objects, and second, a predetermined naming convention is applied to the pathnames of collided objects within the namespace. A winner object of a collision is stored with the pathname of the actual object (e.g., “/object”) in the namespace, and the loser object is stored with a pathname derived from the actual object (e.g., “/object.collision”) and the collision flag of the loser object is set to mark the loser object within the namespace. Accordingly, winners and losers of collisions in the namespace can be identified by searching system metadata for collision flags which indicate collision losers, and associated winners can be identified based on the pathname of the losers.

Abstract: A data management system that is enabled such that the user can select a data source node, a repository and a data path, choose policies for each and distribute the policies to be managed by the management system.

Abstract: In some examples, a plurality of content properties may be used for managing indexing of object data, such as a plurality of files. Each content property may include an expression for extracting data values from specific data fields in the object data. Further, each content property may include a name that may be used for indexing the objects using the extracted data values. For instance, multiple content properties may have the same name, but may each have different expressions for extracting different data values from different data fields. Accordingly, the content properties may be used to extract desired data values from the objects for indexing. When a search query is received including a content property name and a specified value, one or more of the objects that are indexed with the specified value may be searched.

Abstract: In one aspect, the invention is directed to a method of expanding storage for filesystems in a fine-grained, scalable manner. The method includes determining, by a file server, a run bias for a span, wherein the run bias indicates a number of contiguous chunks of memory associated with an entry in an address translation table for a filesystem. The method includes receiving, by the file server, a request for an expansion of memory for the filesystem. The method includes scoring, by the chunk allocator, each stripe set in a group of stripe sets based at least in part on a number of unused chunks on the stripeset and a number of chunks on the stripeset being used by the filesystem. The method includes allocating, by the chunk allocator, a chunk on the stripeset with the highest score, wherein the allocated chunk lies outside of runs reserved for other filesystems.

Abstract: In some examples, a system may include multiple types of data restore point intervals, such as daily, weekly, monthly, etc. The system may store, for a first version of an object, a first time at which the object is received and a first flag for a first restore point interval. Subsequently, the system may store for a second version of the object, a second time at which the second object is received and a second flag for the first restore point interval. The system may clear a flag based on the second time and the first time being within a same time interval corresponding to the first restore point interval. An object version for which the flags have been cleared may be deleted from the storage. The stored times may be used to determine, at least partly, one or more retained object versions to provide for a selected restore point.

Abstract: The present disclosure relates to management of cloned objects and corresponding snapshot objects in file systems by a file server. Aspects may relate to one or more processes for managing file system objects of a file system in a data storage system comprising a file system server, wherein the file system server comprises: a computer system including a processor configured to execute an operating system and further software components executed on the operating system, and a programmable logic device interfacing with the computer system and including a file system management unit configured to manage a file system.

Abstract: At the target side, a first instruction to replicate a first target snapshot-file of a target snapshot-file tree of the target file system is received, the first target snapshot-file of the target file system being associated with a first source snapshot-file of the source file system which has been modified in the source file system. One or more data blocks which are owned by a second target snapshot-file and which are shared between the first target snapshot-file and the second target snapshot-file are identified, the second target snapshot-file being an ancestor of the first target snapshot-file in the target snapshot-file tree. Then, at the target side, ownership of the one or more identified data blocks is transferred from the second target snapshot-file to the first target snapshot-file.

Abstract: A system for continuously monitoring and searching social networking media allowing at least one client to access the system through a respective connection link and for connecting to at least one social networking media through a connection link. The system further comprises a connecting module comprising at least one connecting unit to connect to the at least one social network media for receiving continuously for a time selected by the activity data shared in real time and/or posted by users of the social network media; and a processing module comprising a processing unit, configured to process continuously for the time selected by the client the received activity data based on at least one pre-determined monitoring criterion selected by the client from a number of predetermined criteria, and a notification unit configured to send a notification to the client when the received activity data meet the selected monitoring criteria.

Abstract: A storage system comprises: a controller; a memory; one or more objects, each object having content data and metadata which includes system metadata; and a policy which governs writing of the content data and metadata of the one or more objects from the storage system to an external storage. The policy includes a configurable criterion for decoupling of the content data and the metadata of a given object and a rule for determining storage locations for the content data and the metadata between the storage system and the external storage in a decoupled manner if the content data and the metadata of the object are decoupled. The configurable criterion is based on an attribute of the metadata of the object. The controller is operable to execute the policy against the objects and to apply the rule to determine storage locations for the content data and metadata of a decoupled object.

Abstract: In some examples, a first system may store a data object according to a first data protection level and may send the data object to a geographically remote second system for storing as a replicated data object. Based on determining that a condition for transitioning the data object to a different data protection level has been met, the first system may check a local data structure to determine that the data object was sent to the second system. Based on determining that the data object was sent for replication to the second system, the first system may send a request to the second system to verify storage of the replicated data object at the second system. Based on receiving a reply indicating storage of the replicated data object at the second system, the first system may transition the data object to the different data protection level.

Abstract: In some examples, a multi-node system may access physical storage divided into extents and further arranged into extent groups that may be allocated on demand as thin provisioned storage in response to write requests. Protection class instances are set with specified data protection capabilities. Each instance acts as a logical unit having a distinct addressable block storage space from the extent groups allocated thereto. The extents in an extent group to be allocated to a given protection class instance may vary depending on the protection class capabilities. Management information for the extents, extent groups, and protection classes may be stored in mirrored devices separate from the write data stored in the extents for providing redundant protection to the management information and for increasing the availability of write data in the event of a failure that may cause data loss at one or more locations in the system.