Hitachi Vantara Corporation

Hitachi Data Systems Corporation

Yury Kats

Benjamin Isherwood

Rich Rogers

Sowmya Manjanatha

Jeffrey M Crump

Jordan Diehl

Steven Haapaoja

Cody Lee

Jared Cohen

Frank Fodera

In some examples, a computer system may receive an indication to present a user interface presenting data for a plurality of metrics related to at least one of a status or a performance of a storage system. The computer system may determine a status of a workflow that processes messages received from the storage system. Further, the computer system may determine an end time for a plurality of metric visualizations to present in the user interface based on the status of the workflow. The computer system may render the plurality of metric visualizations, with each metric visualization having the determined end time. Further, the computer system may provide the plurality of rendered metric visualizations for presentation in the user interface on a display.

User interface optimization for delayed data

In some examples, a system may include at least one class of storage that is configured for having freed storage space reclaimed to enable reuse of the freed storage space. For instance, the system may determine whether a volume corresponding to the at least one class of storage is used to store system data or user data. If the volume is used to store user data, then the system may determine whether any of the user data has been deleted from the volume. If data has been deleted from the volume, the system may determine whether an available capacity of the volume is less than a remaining capacity threshold before performing reclamation on the at least one storage device corresponding to the volume. Alternatively, if the volume is used to store system data, the system may perform reclamation based on an elapsed period of time since the last reclamation.

Adaptive storage reclamation

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.

System and method of collision management in a namespace of a storage system

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.

Content class for object storage indexing system

A redundant array of independent nodes are networked together. Each node executes an instance of an application that provides object-based storage. The nodes are grouped into systems each having multiple nodes. A search index is provided in each system for locating objects within the system. A method of managing the search index comprises splitting the search index into shards to be divided among a plurality of regions (). The regions are larger in number than the nodes in the system. Each region has a master and at least one backup copy of one of the shards. A shard core is a master or backup copy of a shard. The method further comprises distributing the shard cores to the nodes, and providing a region mapping table in each node in the system to map the shard cores to the nodes in which the shard cores are stored ().

Highly available search index with storage node addition and removal

A storage system stores objects and copies of objects on the storage system and other storage systems external to the storage system. The storage system stores the copies in storage pools of volumes, which are organized into one or more tiers. The configuration settings of each tier and each pool within the tier may be configured according to a user's preferences. In one example, the number of copies of data content and the number copies of metadata associated with the data content an individual pool stores may be specified. When objects are migrated between tiers, the objects are stored among the storage pools of the tiers. If the number of data content copies or metadata copies is increased, the data or metadata is copied from a determined copy source and if the number of copies decreases, the data is removed from the volumes in the pools.

Service plan tiering, protection, and rehydration strategies

A storage system comprises a controller; a memory; and one or more objects each including content data and metadata. The metadata is used to construct user-defined content properties, each content property providing an ability to extract a specific metadata field from the objects by referring to a user-defined content property name of the content property. The content properties are organized into user-defined content classes, each content class grouping a set of content properties into a named category under a user-defined content class name. The controller is operable to index the content properties of the content classes to create an index. The content properties being indexed are identified by the content property names. In some embodiments, the controller is operable to de-dupe the index, for content properties having same values expressed differently in different metadata formats, by directing the differently expressed values to same index field under same content property name.

Growing community of inventors

Belmont, MA, United States of America

Yury Kats