Abstract:
A layout of a transaction log enables efficient logging of metadata into entries of the log, as well as efficient reclamation and recovery of the log entries by a volume layer of a storage input/output (I/O) stack executing on one or more nodes of a cluster. The transaction log is illustratively a two stage, append-only logging structure, wherein the first level is non-volatile random access memory (NVRAM) embodied as a NV log and the second stage is disk, e.g., solid state drive (SSD). The layout of the logging structure facilitates steady-state logging of metadata managed by the volume layer and crash recovery. Steady-state logging of metadata into the log entries occurs while the storage I/O stack of a node actively processes I/O requests, while crash recovery of the log entries occurs after an unexpected shutdown of the node.
Abstract:
Methods and systems for restoring storage objects are provided. The method includes determining if a source storage object and a target storage object are located within a same storage volume, where the source storage object is associated with a first drive and the target storage object is associated with a second drive; and using a point in time copy of the source storage object for restoring the source storage object at the second drive.
Abstract:
Methods and systems for a storage server are provided. One method includes storing data at a first storage tier by a processor executable storage operating system; tracking the data stored at the first storage tier for moving the data to a second storage tier; transferring the data from the first storage tier to the second storage tier; and updating a data structure that tracks a transfer block number of a block that stores the data, where the transfer block number is based on a virtual identifier, a generation count and an offset value of a storage chunk that is a portion of a physical volume block number address space.
Abstract:
A method and system for a provisioning advisor are described which estimates the input/output operation performance of a workload on a storage system. A regression module in a provisioning advisor estimates a maximum IOPS on the storage system for buckets, or combinations of values, for various characteristics of the workloads running on the system by modeling a relationship between the workload characteristics and performance metrics gathered from the storage system. A performance module can use the estimated maximum IOPS for each bucket to update a set of working tables for the provisioning advisor, which can then be used to predict the input/output performance of a new workload to be provisioned on the storage system.
Abstract:
Methods and systems for a networked storage environment are provided. As an example, one method includes registering a resource model with an application programming interface (API) server, where the resource model includes information regarding a plurality of resources used for storing data in a networked storage system having a plurality of storage devices; executing a data source service by the API server for obtaining information regarding any of the plurality of resources of the networked storage system, where the data source service obtains information from different data sources associated with different storage system platform types; and in response to a request, providing information regarding any metrics that are used for monitoring the plurality of resources by the API server.
Abstract:
To leverage the attributes of object storage for applications/systems created to interface with a network files system, an object storage backed file system can accept the defined file system commands from the applications/systems and transform the file system commands into requests that target object storage. The file system is “backed” by object storage because attributes and content of file system entities are stored in objects. For instance, content data and metadata of a file are stored in objects in object storage. This object storage backed file system can be considered a bridge between a client perceived hierarchical file system namespace and a flat namespace of an object storage.
Abstract:
A system and method for planning and configuring the components of a modular computing system is provided. In some embodiments, the method for planning an implementation of a modular computing system comprises presenting a user interface at a display device, the user interface including a plurality of user-selectable objects, each of the user-selectable objects representing a component of the modular computing system. A user selection is received via a user input device. The user selection is from among the user-selectable objects and specifies one of an enclosure, an existing component, and a future component of the modular computing system. A representation of the specified one of an enclosure, an existing component, and a future component is displayed at a display device. The user selection is verified with respect to an implementation guideline. An indicator of whether the user selection meets the implementation guideline is displayed at the display device.
Abstract:
Methods, systems, and machine-readable medium are disclosed for creating and providing dynamic hierarchical navigation schemes in storage management systems. A mapping data structure is maintained to store hierarchical relationship mapping within a storage management system, allowing users to customize their interactions with the storage system. The method, includes receiving a user-defined navigation preference to view an attribute of a second storage object from a navigation screen defined for a first storage object; updating a mapping data structure for storing a hierarchical relationship of a second storage object, based on the user-defined navigation preference; and presenting the attribute of the second storage object at the navigation screen for the first storage object.
Abstract:
During a storage redundancy giveback from a first node to a second node following a storage redundancy takeover from the second node by the first node, the second node is initialized in part by receiving a node identification indicator from the second node. The node identification indicator is included in a node advertisement message sent by the second node during a giveback wait phase of the storage redundancy giveback. The node identification indicator includes an intra-cluster node connectivity identifier that is used by the first node to determine whether the second node is an intra-cluster takeover partner. In response to determining that the second node is an intra-cluster takeover partner, the first node completes the giveback of storage resources to the second node.
Abstract:
A method, non-transitory computer readable medium, and computing device that determines when a software failure associated with a virtual storage controller has occurred. At least a portion of a transaction log corresponding to the virtual storage controller is stored in a stable storage device, when the determining indicates that the software failure associated with the virtual storage controller has occurred. A determination is made when the virtual storage controller has rebooted. The at least a portion of the transaction log is retrieved from the stable storage device, when the determining indicates that the virtual storage controller has rebooted. Thereby, state can be preserved and transactions pending, but not yet committed to storage server devices, can be replayed and proceed with minimal or no impact on the client devices originating the transactions.