Abstract:
Systems and methods for automated firmware update with rollback are described herein. The systems include a plurality of storage zones, each storage zone including a plurality of storage nodes, each storage node including a plurality of storage media. The method includes monitoring storage system activity and parameters and maintaining a data storage system usage and parameter database containing system activity information. When a firmware update is available, data storage system activity is evaluated. Storage nodes needing the firmware update are identified. The firmware update is run on available storage nodes identified as needing the firmware update. The impact of the firmware update is evaluated and a rollback of the firmware update is initiated on all firmware updated storage nodes when parameter variations are significant and/or result in degraded performance.
Abstract:
A failure resilient distributed replicated data storage system is described herein. The storage system includes zones that are independent, and autonomous from each other. The zones include nodes that are independent and autonomous. The nodes include storage devices. When a data item is stored, it is partitioned into a plurality of data objects and a plurality of parity objects calculated. Reassembly instructions are created for the data item. The data objects and parity objects are spread across all nodes and zones in the storage system. Reassembly instructions are also spread across the zones. When a read request is received, the data item is prepared from the lowest latency nodes according to the reassembly instructions. This provides for data resiliency while keeping the amount of storage space required relatively low.
Abstract:
A failure resilient distributed replicated data storage system is described herein. The storage system includes zones that are independent, and autonomous from each other. The zones include nodes that are independent and autonomous. The nodes include storage devices. When a data item is stored, it is partitioned into a plurality of data objects and a plurality of parity objects calculated. Reassembly instructions are created for the data item. The data objects and parity objects are spread across all nodes and zones in the storage system. Reassembly instructions are also spread across the zones. When a read request is received, the data item is prepared from the lowest latency nodes according to the reassembly instructions. This provides for data resiliency while keeping the amount of storage space required relatively low.
Abstract:
A failure resilient distributed replicated data storage system is described herein. The storage system includes zones that are independent, and autonomous from each other. The zones include nodes that are independent and autonomous. The nodes include storage devices. When a data item is stored, it is partitioned into a plurality of data objects and a plurality of parity objects calculated. Reassembly instructions are created for the data item. The data objects and parity objects are spread across all nodes and zones in the storage system. Reassembly instructions are also spread across the zones. When a read request is received, the data item is prepared from the lowest latency nodes according to the reassembly instructions. This provides for data resiliency while keeping the amount of storage space required relatively low.
Abstract:
Systems and methods for data replication in a data storage system having a disjointed network are described herein. The data storage system includes a plurality of clusters each having at least one stationary zone. The data storage system further includes at least one movable zone. Each zone has a plurality of storage nodes, and each storage node has a plurality of storage devices. The system provides for replication according to policies associated with data objects such that data items are stored among a plurality of zones. Movable zone that are disconnected from and reconnected to the other zones and clusters in the storage system are supported.
Abstract:
Systems and methods for storing data in a data storage system that allows dynamic context-based data protection and distribution are disclosed. The method includes receiving a storage request and evaluating whether a storage policy is specified in the storage request. When the storage request specifies a storage policy, the data is stored according to the specified policy. When the storage request does not specify a storage policy, meta data and/or the data item itself may be evaluated to identify a storage policy. When a storage policy has been identified, store the data is stored according to the identified policy. When a storage policy has not been specified and cannot be identified, an error is returned.
Abstract:
Systems and methods for dynamic context based data protection and distribution in which data replication in a multi-zone storage system automatically changes based on historical storage trends and/or external information obtained from third party information sources is described herein. The methods include monitoring third party information sources and evaluating a correlation between event data from the third party information sources and key words that are user provided and/or system derived. A correlation between the event data and data storage history may be evaluated. A storage policy is derived based on the results of the correlation evaluation(s). The derived storage policy and corresponding key words are stored in a database.
Abstract:
A resilient distributed replicated data storage system is described herein. The storage system includes zones that are independent, and autonomous from each other. The zones include nodes that are independent and autonomous. The nodes include storage devices. When a data item is stored, it is partitioned into a plurality of data objects and a plurality of parity objects are calculated. Reassembly instructions are created for the data item. The data objects, parity objects and reassembly instructions are spread across nodes and zones in the storage system according to a policy for the data item. When a zone is inaccessible, a virtual zone is created and used until the intended zone is available. When a read request is received, the data item is prepared from the lowest latency nodes according to the reassembly instructions, and a virtual zone is accessed in place of a real zone when the real zone is inaccessible.
Abstract:
Systems and methods for automated firmware update with rollback are described herein. The systems include a plurality of storage zones, each storage zone including a plurality of storage nodes, each storage node including a plurality of storage media. The method includes monitoring storage system activity and parameters and maintaining a data storage system usage and parameter database containing system activity information. When a firmware update is available, data storage system activity is evaluated. Storage nodes needing the firmware update are identified. The firmware update is run on available storage nodes identified as needing the firmware update. The impact of the firmware update is evaluated and a rollback of the firmware update is initiated on all firmware updated storage nodes when parameter variations are significant and/or result in degraded performance.
Abstract:
Systems and methods for storing data in a data storage system that allows dynamic context-based data protection and distribution are disclosed. The method includes receiving a storage request and evaluating whether a storage policy is specified in the storage request. When the storage request specifies a storage policy, the data is stored according to the specified policy. When the storage request does not specify a storage policy, meta data and/or the data item itself may be evaluated to identify a storage policy. When a storage policy has been identified, store the data is stored according to the identified policy. When a storage policy has not been specified and cannot be identified, an error is returned.