Abstract: Example object storage systems, bookkeeping engines, and methods provide quota usage monitoring for control entities, such as accounts, users, and buckets. An object data store is configured to enable control entities to access data objects associated with each control entity. Data objects are mapped to the control entities and the data objects are processed to identify object usage values corresponding to each combination of data object and control entity. Total usage values are calculated for each control entity and used to determine a data object access response for a target data object and associated control entities.

Abstract: Example distributed storage systems, replication managers, and methods provide versioning validation for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A versioned write request message is sent to a second object data store and a response is received. The versioning-enabled status of the second object data store is determined from the response message and, if the versioning enabled status is invalid, any residual object versions in the second object data store are deleted based on a delete request.

Abstract: Example distributed storage systems, version control managers, and methods provide persistent version control for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A version control manager is configured to determine a creation timestamp for each of the plurality of sequential versions and store a persistent version field for each. The persistent version field remains associated with each of the plurality of sequential versions when transferred from the first object data store to a second object data store.

Abstract: Example object storage systems, bookkeeping engines, and methods provide quota-based access control for control entities, such as accounts, users, and buckets. An object data store is configured to enable control entities to access data objects associated with each control entity. Quota thresholds and usage values are determined for control entities and used to determine a quota status. Quota status is used to determine data object access response based on the requesting control entities.

Abstract: Example distributed storage systems, replication managers, and methods provide replication configurations for data transfers to multiple heterogeneous data stores. A first object data store includes multiple storage buckets for replication to different data stores. Different target storage systems have different system configurations that are different than the native system configuration. For each storage bucket and corresponding target storage system, a native replication operation is translated to a target replication operation compatible with the target system configuration and the target replication operation is used to replicate the selected storage bucket to the corresponding target storage system.

Abstract: Example object storage systems, bookkeeping engines, and methods provide quota enforcement for control entities, such as accounts, users, and buckets. An object data store is configured to enable control entities to access data objects associated with each control entity. Quota thresholds associated with requesting control entities are determined. Object usage values corresponding to the quota thresholds are determined. Data object access requests are denied responsive to object usage values exceeding quota thresholds for the requesting control entities.

Abstract: Example object storage systems, meta object generators, and methods provide versioned meta objects for internal operational data that may be replicated between data object stores. A meta object may be generated that includes meta object data, such as internal operational data. A meta object identifier may be assigned to the meta object. A first version identifier may be associated with the meta object data and a second version identifier may be associated with a marker for the meta object, where the marker prevents exposure as a user data object.

Abstract: Example object storage systems, replication managers, and methods provide meta objects for priority replication of configuration data between data object stores. A meta object may be generated that includes configuration data. Data objects are selected for replication from a first replication queue. Meta objects associated with the data objects in the first replication queue are replicated, independent of the first replication queue, between object data stores.

Abstract: The described methods, systems, and other aspects can advantageously provide balanced multi-stage processing of non-uniform object data. An example method may receive a list of buckets. Each of the buckets in the list of buckets can store one or more restorable objects. The method further comprises distributing the list of buckets to the two or more second nodes; determining a number of the one or more restorable objects in each bucket; determining a size of the one or more restorable objects in each bucket; generating batches of to-be-restored data objects based on the determined number of the one or more restorable objects in each bucket and the determined size of the one or more restorable objects in each bucket; and distributing the batches among the two or more second nodes for storage-related task processing.

Abstract: Example distributed storage systems, replication managers, and methods provide replication configurations for data transfers to multiple heterogeneous data stores. A first object data store includes multiple storage buckets for replication to different data stores. Different target storage systems have different system configurations that are different than the native system configuration. For each storage bucket and corresponding target storage system, a native replication operation is translated to a target replication operation compatible with the target system configuration and the target replication operation is used to replicate the selected storage bucket to the corresponding target storage system.

Abstract: The described methods, systems, and other aspects can advantageously provide balanced multi-stage processing of non-uniform object data. An example method may receive a list of buckets. Each of the buckets in the list of buckets can store one or more restorable objects. The method further comprises distributing the list of buckets to the two or more second nodes; determining a number of the one or more restorable objects in each bucket; determining a size of the one or more restorable objects in each bucket; generating batches of to-be-restored data objects based on the determined number of the one or more restorable objects in each bucket and the determined size of the one or more restorable objects in each bucket; and distributing the batches among the two or more second nodes for storage-related task processing.

Abstract: Example object storage systems, replication managers, and methods provide meta objects for priority replication of configuration data between data object stores. A meta object may be generated that includes configuration data. Data objects are selected for replication from a first replication queue. Meta objects associated with the data objects in the first replication queue are replicated, independent of the first replication queue, between object data stores.

Abstract: Example object storage systems, meta object generators, and methods provide versioned meta objects for internal operational data that may be replicated between data object stores. A meta object may be generated that includes meta object data, such as internal operational data. A meta object identifier may be assigned to the meta object. A first version identifier may be associated with the meta object data and a second version identifier may be associated with a marker for the meta object, where the marker prevents exposure as a user data object.

Abstract: Example object storage systems, bookkeeping engines, and methods provide quota-based access control for control entities, such as accounts, users, and buckets. An object data store is configured to enable control entities to access data objects associated with each control entity. Quota thresholds and usage values are determined for control entities and used to determine a quota status. Quota status is used to determine data object access response based on the requesting control entities.

Abstract: Example object storage systems, bookkeeping engines, and methods provide quota enforcement for control entities, such as accounts, users, and buckets. An object data store is configured to enable control entities to access data objects associated with each control entity. Quota thresholds associated with requesting control entities are determined. Object usage values corresponding to the quota thresholds are determined. Data object access requests are denied responsive to object usage values exceeding quota thresholds for the requesting control entities.

Abstract: Example object storage systems, bookkeeping engines, and methods provide quota usage monitoring for control entities, such as accounts, users, and buckets. An object data store is configured to enable control entities to access data objects associated with each control entity. Data objects are mapped to the control entities and the data objects are processed to identify object usage values corresponding to each combination of data object and control entity. Total usage values are calculated for each control entity and used to determine a data object access response for a target data object and associated control entities.

Abstract: Example distributed storage systems, version control managers, and methods provide persistent version control for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A version control manager is configured to determine a creation timestamp for each of the plurality of sequential versions and store a persistent version field for each. The persistent version field remains associated with each of the plurality of sequential versions when transferred from the first object data store to a second object data store.

Abstract: Example distributed storage systems, replication managers, and methods provide versioning validation for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A versioned write request message is sent to a second object data store and a response is received. The versioning-enabled status of the second object data store is determined from the response message and, if the versioning enabled status is invalid, any residual object versions in the second object data store are deleted based on a delete request.

Abstract: A method of managing a storage system having one or more storage devices includes receiving a request to access, in a tiered data structure, a data object and one or more attributes of the data object and processing the access request. The request includes a first key value for the data object and respective second key values for the one or more attributes of the data object. Modified key values for the attributes of the data object are generated in accordance with at least a portion of the first key value and used to access tree entries for the data object attributes in one or more leaf nodes of the tiered data structure. A tree entry for the data object is also accessed from the same set of one or more leaf nodes.

Abstract: An apparatus includes a data sequencing engine configured to receive first data and an identification of a first data container associated with the first data and to allocate the first data to a first data stream of multiple data streams based on the identification. The apparatus further includes at least one memory configured to store the first data container. The data sequencing engine is further configured to cause the at least one memory to send data in the first data stream to a flash memory in response to detecting a data size of the first data stream satisfies a threshold.