Abstract: Example implementations described herein facilitate a drive unit to share physical mediums (e.g. solid state drives) among multiple storage controllers or storage nodes in a distributed storage system, while keeping them physically independent in a redundancy group to avoid single point of failure, by providing an interface to notify redundancy group to the drive unit.

Abstract: Embodiments of the present disclosure generally relate to a target device handling overlap write commands. In one embodiment, a target device includes a non-volatile memory and a controller coupled to the non-volatile memory. The controller includes a random accumulated buffer, a sequential accumulated buffer, and an overlap accumulated buffer. The controller is configured to receive a new write command, classify the new write command, and write data associated with the new write command to one of the random accumulated buffer, the sequential accumulated buffer, or the overlap accumulated buffer. Once the overlap accumulated buffer becomes available, the controller first flushes to the non-volatile memory the data in the random accumulated buffer and the sequential accumulated buffer that was received prior in sequence to the data in the overlap accumulated buffer. The controller then flushes the available overlap accumulated buffer, ensuring that new write commands override prior write commands.

Abstract: A method for verifying data includes obtaining, by a backup agent, a backup verification trigger for a backup stored in a backup storage system, in response to the backup verification trigger, obtaining backup metadata associated with the backup, performing a hierarchical structure data mapping based on the backup metadata to obtain a hierarchical structure associated with the backup, performing, using the hierarchical structure, a backup verification to generate a backup health state of the backup, after the backup verification is generated: making a determination, based on the backup verification, that the backup health state is not in a healthy state, and in response to the determination, performing a remediation of the backup policies.

Abstract: A method is provided for managing availability of runtime asset data used by client applications hosted on workstations of an industrial system, the method including distributing runtime asset data about assets of the industrial system received at the plurality of workstations among runtime asset data caches associated with the client applications. At least a portion of locally stored runtime asset data stored on a local runtime asset data cache is replicated and stored remotely on the runtime asset data cache associated with another client application. The locally stored runtime asset data is periodically evaluated to determine if it is up-to-date, and in response to determining it is not up-to-date, the locally stored runtime asset data is updated by requesting and retrieving a replicated and updated version of the locally stored runtime asset data from the runtime asset data cache remotely storing the replicated version.

Abstract: A memory system includes a plurality of physical memories and a memory controller. The memory controller is configured to configure one or more logical memories used by one or more programs, respectively, to which areas of the plurality of physical memories are allocated. The memory controller is configured to calculate first data indicating a response performance of the plurality of physical memories, calculate second data indicating a degree of influence of waiting for access to the one or more logical memories, the degree of influence being on a processing performance of the one or more programs, and control allocation of the areas of the plurality of physical memories to the one or more logical memories on the basis of the first data and the second data.

Abstract: Providing copy data candidates appropriate for a user request. Included are an operational portal that registers user request information; a data catalog that manages information about multiple copy data located at sites configuring a hybrid cloud system; a data allocation service that allocates duplicated copy data to the sites; and a guideline management service that selects a copy data candidate appropriate for user request information. The guideline management service acquires information about copy data containing the same data as user request information from the data catalog and verifies whether there is a copy data candidate satisfying the user request information. When there is consequently no copy data candidate satisfying the user request information, the copy data is allocated to the site on condition that the copy data is optimal enough to satisfy a generation schedule and a processing speed of a copy data candidate satisfying the user request information.

Abstract: Methods, computer program products, computer systems, and the like are disclosed that provide for improved write performance in erasure-coded storage systems in an efficient and effective manner. These can include identifying a data segment, identifying metadata, persisting the data segment to a storage system, storing the metadata in the journal, and persisting the metadata to the storage system. In such embodiments, the metadata is associated with the data segment by virtue of the metadata comprising a fingerprint of the data segment. Further, in such embodiments, the persisting the data segment to the storage system is performed without storing the data segment in a journal, and the storage system is an erasure-coded storage system.

Abstract: Techniques are provided for multi-tier write allocation. A storage system may store data within a multi-tier storage environment comprising a first storage tier (e.g., storage devices maintained by the storage system), a second storage tier (e.g., a remote object store provided by a third party storage provider), and/or other storage tiers. A determination is made that data (e.g., data of a write request received by the storage system) is to be stored within the second storage tier. The data is stored into a staging area of the first storage tier. A second storage tier location identifier, for referencing the data according to a format utilized by the second storage tier, is assigned to the data and provided to a file system hosting the data. The data is then destaged from the staging area into the second storage tier, such as within an object stored within the remote object store.

Abstract: A storage array packs multiple non-full-size front-end tracks into slices that contain multiple back-end tracks. A greedy first fit packing algorithm is used to find packing solutions that are cached and ranked. The cached, ranked packing solutions are used by attempting to find matches with bucketed front-end tracks to be relocated. New packing solutions are generated and cached when matches cannot be found. Packing solutions may be shared outside the domain in which they are discovered.

Abstract: Described is a system (and method) for efficient object storage management when backing up data to a cloud-based object storage. The system may be implemented as part of a server (or gateway) that provides a backup service to a client device by acting as an intermediary when backing up data from the client device to a third-party cloud-based object storage. The system may implement various specialized procedures to efficiently store backup data as objects within the object storage. The procedures may include packing client data into objects of a consistent size to improve storage performance. The system may also improve storage performance and conserve storage by analyzing the data stored within an object and reallocating the data as necessary. More particularly, the system may efficiently reallocate data to new objects when the amount of live data within an object falls below a predetermined threshold.

Abstract: An information handling system includes a first Dual In-Line Memory Module (DIMM) on a first memory channel of the information handling system, and a second DIMM on a second memory channel of the information handling system. A processor trains the first memory channel to a first speed based upon a first performance level of the first DIMM, trains the second memory channel to a second speed based upon a second performance level of the second DIMM, and allocates a portion of the first DIMM to the application based upon the first speed.

Abstract: Techniques are provided for block allocation for persistent memory during aggregate transition. In a high availability pair including first and second nodes, the first node makes a determination that control of a first aggregate is to transition from the first node to the second node. A portion of available free storage space is allocated from a first persistent memory of the first node as allocated pages within the first persistent memory. Metadata information for the allocated pages is updated with an identifier of the first aggregate to create updated metadata information reserving the allocated pages for the first aggregate. The updated metadata information is mirrored to the second node, so that the second node also reserves those pages. Control of the first aggregate is transitioned to the second node. As a result, the nodes do not attempt allocating the same free pages to different aggregates during a transition.

Abstract: An illustrative live synchronization feature uses file system block-level backup copies, snapshot techniques, change tracking, and volume-level granularity to ensure the integrity of destination volumes. Two protection mechanisms guard the destination data and ensure consistency from one live sync restore to the next. First, an inter-job software snapshot captures the destination volume image after each restore. The snapshot is created at the very end of each live sync restore and is reverted at the beginning of the next live sync restore. A second and more granular protection mechanism uses intra-job block monitoring to detect, and later to reverse, changes that the snapshots cannot capture. This second mechanism acts as a mini-block-level restore nested inside another block-level restore. This dual approach ensures that each incremental live sync restore finds the destination volume with a guaranteed pristine image identical to where the preceding live sync restore left it.

Abstract: Embodiments of the present invention provide a method and system for managing a storage area. In one embodiment of the present invention, there is provided a method for managing a storage areas, comprising: obtaining a storage area in a storage system according to a predefined dividing rule; determining status regarding whether the storage area has been used; setting a status identifier for the storage area based on the use status; and managing the storage area based on the status identifier. In another embodiment, there is proposed a system for managing a storage area, comprising: one or more processors; a memory coupled to at least one processor of the one or more processors; computer program instructions stored in the memory which, when executed by the at least one processor, cause the system to execute a method for managing a storage area.

Abstract: A backup system for backing up data on a computer system, comprising: a plurality of storage devices, the storage devices can be of any type known in the industry such as USB, SATA, SD etc. Storage devices may be built in the device or external devices. The same system may have storage devices that are of the same type (all internal or all external) or a mixture (some internal some external). One or more connector for connecting the plurality of storage devices to the computer system. The storage devices may each have a unique connector (wired or wireless) to the computer system or alternatively, one connector can be connected each time to another storage device. The system also comprises a control module for controlling the connection between the plurality of storage devices to said computer system such that at any given time at least one but not all storage devices are connected to the computer system.

Abstract: A data storage device includes a memory device including a normal data region and a mapping data region, the normal data region being configured to store normal data, the mapping data region being configured to store mapping data; a host request managing device configured to manage a read/write request from a host; a mapping managing device configured to cache a part of the mapping data and to manage mapping information according to a request from the host request managing device; and a memory controller configured to manage an operation of the memory device according to a request from at least one of the host request managing device and the mapping managing device.

Abstract: Technologies are provided for storing data by alternating the performance of data write operations using multiple clusters of storage devices. Data is written to internal buffers of storage devices in one cluster while data stored in buffers of storage devices in another cluster is transferred to the storage devices' permanent storages. When available buffer capacity in a cluster falls below a specified threshold, data write commands are no longer sent the cluster and the storage devices in the cluster transfer data stored in their buffers to their permanent storages. While the data is being transferred, data write commands are transmitted to other clusters. When the data transfer is complete, the storage devices in the cluster can be scheduled to receive data write commands again. A cluster can be selected for performing a given data write request by matching the attributes of the cluster to parameters of the data write request.

Abstract: The present disclosure discloses a method, a system, and a solid-state drive for data processing. The method includes detecting the user operations on a first storage area which is visible to an operating system in a solid-state drive; if the user operation is a reading or writing operation, keeping the data of the first storage area and the data of a mirrored data storage area of a second storage area to be synchronization; if the user operation is a deleting operation or a TRIM operation, keeping the data of the first storage area and the data of the mirrored data storage area of the second storage area to be synchronization, and backing up the deleted data from the first storage area to a deleted data storage area of the second storage area. The second storage area is set to be invisible to the operating system in the solid-state disk.

Abstract: A method for managing storage devices in a backup storage system includes obtaining, by a backup agent, a backup storage initiation request, identifying, in response to the backup storage initiation request, an initial grouping amount for a plurality of application types, generating a plurality of backup storage deduplication pools based on the initial grouping amount, generating a buffer pool, and generating a plurality of deduplication pool metadata mappings based on the plurality of backup storage deduplication pools, wherein a backup storage deduplication pool of the plurality of backup storage deduplication pools comprises a storage device, and wherein the buffer pool comprises a plurality of storage devices.

Abstract: Methods, systems, apparatus, including computer programs encoded on computer storage media, for reclaiming storage space in a storage environment. In one aspect, the method includes actions of aggregating data that is indicative of access to one or more data objects, determining a future storage cost associated with each of a plurality of data objects, determining an access window for each of the plurality of data objects, identifying a data object based on (i) the future storage cost that satisfies a predetermined threshold and (ii) a data object access window, providing a notification to a user device that requests feedback from a user indicating whether the data object can be deleted, and in response to receiving data that indicates that the data object can be deleted, generating an instruction to cause deletion of the data object upon the expiration of the access window.