Abstract: Embodiments are described for a executing a processing job using one or more nodes of a storage area network using computing resources on the SAN that are predicted to be idle. A predictive model is generated by monitoring idle states of resources of nodes of the SAN and using machine learning to build the predictive model. A scheduler executes jobs on one or more nodes of the SAN with sufficient predicted idle resources to process the job, in accordance with resource requirements and job attributes in a manifest of the job. If a job cannot be completed during a window of time that the necessary resources are predicted to be idle, or if one or more resources become unavailable, the job can be paused and resumed, migrated to another node, or restarted at a later time when the required resources to complete the job are predicted to be idle.

Abstract: Embodiments are described for dynamically allocating and reallocating system resources between production work tasks and administrative tasks using policies. A resource monitor continuously monitors all resources in a computing system, and whether the resources are used for production work or administrative tasks. A policy can define resources needed to execute an administrative task and conditions which can be used to determine whether or not the administrative command is allocated the resources, even at the expense of a negative impact to production work.

Abstract: Systems and methods for scheduling multiple flows in a computing system or for allocating resources to the flows in the computing system. Each flow may be associated with a target priority and a target performance. A current priority can be determined for each flow and resources are allocated based on the highest current priority. Over time, the current priorities change and each flow will receive resources as the flows are scheduled for execution. No flow is starved of resources.

Abstract: Embodiments are described for a multi-node file system, such as a clustered or distributed file system, with a file system buffer cache and an additional host-side tier non-volatile storage cache such as 3DXP storage. Cache coherency can be maintained by one of three models: (i) host-side tier management, (ii) file system management, or (iii) storage array management. performing a storage tier-specific file system action in a file system that comprises a namespace that spans multiple tiers of storage.

Abstract: Embodiments are described for a multi-node file system, such as a clustered or distributed file system, with a file system buffer cache and an additional host-side tier non-volatile storage cache such as 3DXP storage. Cache coherency can be maintained by one of three models: (i) host-side tier management, (ii) file system management, or (iii) storage array management. performing a storage tier-specific file system action in a file system that comprises a namespace that spans multiple tiers of storage.

Abstract: A storage node such as a storage array or storage server has storage controllers with heterogeneous parallel processors. The CPUs may be used to perform read and write operations. GPUs are used to produce transformed data from raw data. The GPUs may be used to perform various analytic calculations. The GPUs may be interconnected via dedicated communication links.

Abstract: Systems and methods are disclosed for associating one or more storage-based services with a storage unit accessible by a primary “tier 1” storage device. A storage-based service can include deduplication, compression, data conversion, statistical analysis of the data to be stored, or other storage-based service. A storage unit can be a disk, a file, a virtual disk, or a logical unit of storage (LUN). A virtual machine within the primary “tier 1” storage can perform the one or more storage-based services associated with the storage unit.

Abstract: A backup engine of a first storage system receives a request to perform a backup session from the first storage system to a second storage system based on a backup service level objective (SLO) that has been configured for the backup session. In response to the request, it is determined that a first backup resource allocated for the backup session by the first storage system cannot satisfy the SLO based on statistics of prior backup sessions in view of characteristics of the backup session to be performed. A dynamic resource allocation (DRA) module is to dynamically perform a first DRA to modify the first backup resource to satisfy the SLO. The backup engine then initiates the backup session by transmitting backup data from the first storage system to the second storage system using the modified first backup resource.

Abstract: A technique provides data storage system services in data storage equipment. The technique involves performing, by processing circuitry of the data storage equipment, data storage operations on a production volume in response to data storage commands from a set of application servers (e.g., external host computers). The production volume stores application server data utilized by the set of application servers. The technique further involves running, by the processing circuitry of the data storage equipment, an instance of a virtual backup appliance within the data storage equipment while the data storage operations are performed on the production volume in response to the data storage commands. The technique further involves generating, by the processing circuitry of the data storage equipment, backups of the production volume via the instance of the virtual backup appliance running within the data storage equipment.

Abstract: A system, computer program product, and computer-executable method of balancing Input/Output (I/O) loads for cloud data storage systems including a plurality of hosts and a plurality of data storage arrays, the system, computer program product, and computer-executable method including monitoring, via a first host of the plurality of hosts, a status of a first data storage array of the plurality of data storage arrays, upon detecting a performance issue with the first data storage array, notifying a cloud manager of the first data storage array, wherein the cloud manager is in communication with each of the plurality of hosts and each of the plurality of data storage arrays, monitoring, via the cloud manager, the performance issue, and determining, via the cloud manager, whether to move at least one LUN from the first data storage array.

Abstract: A backup engine of a first storage system receives a request to perform a backup session from the first storage system to a second storage system based on a backup service level objective (SLO) that has been configured for the backup session. In response to the request, it is determined that a first backup resource allocated for the backup session by the first storage system cannot satisfy the SLO based on statistics of prior backup sessions in view of characteristics of the backup session to be performed. A dynamic resource allocation (DRA) module is to dynamically perform a first DRA to modify the first backup resource to satisfy the SLO. The backup engine then initiates the backup session by transmitting backup data from the first storage system to the second storage system using the modified first backup resource.

Abstract: Exemplary methods for data migration from a first storage system to a second storage system include maintaining a database containing deduplication information associated with a plurality of remote target storage systems. In one embodiment, the methods include identifying a plurality of storage devices of the first storage system as candidates to be migrated to the second storage system based on access patterns of the storage devices at the first storage system, and selecting one or more storage devices from the identified candidates to be migrated to a second one of the plurality of remote target storage systems that is selected based on the deduplication information of the database. In one embodiment, the methods further include migrating one or more datasets stored at the selected one or more storage devices to the second storage system.

Abstract: According to one embodiment, a secondary primary storage system monitors replicated data received from a primary storage system, where the primary storage system provides primary storage services to a host device and the second storage system operates as a redundant storage system. In response to determining that no replicated data has been received from the primary storage system over a first predetermined period of time, the secondary primary storage system determines an amount of read/write data requests have been received from the host device for a second period of time. The secondary primary storage system transitions into a second primary storage system in response to determining the amount of read/write data requests received from the host exceeds a predetermined threshold.

Abstract: Resources are optimized in an integrated data protection system having a production host, primary storage and a backup appliance for backup and restore of lost data to a selected restore point. Data tracks in primary storage having changed data are pushed to backup storage with a changed-tracks bitmap mapping the changed tracks. A selected restore capacity is reserved on a restore device, but the restore device is only provisioned for a capacity sufficient to store changed tracks corresponding to the selected restore point, thus obviating the creation and storing of metadata for the unprovisioned capacity. This conserves significant storage and memory capacity and reduces processing requirements.

Abstract: A method in a backup engine is described. The method includes receiving a data access request for a data element in a logical storage volume for one of a read or write operation, determining an affinity group associated with the data element based on an affinity group list indicating a physical storage volume for the data element based on the data address range for the data element, determining a first frontend adapter identifier (ID) from the first affinity group associated with the data element, the first frontend adapter ID identifying a first frontend adapter associated with a first physical storage volume, and transmitting the data access request to the first frontend adapter based on the first frontend adapter ID to execute the data access request on the first physical storage volume.

Abstract: Exemplary methods for improving cache utilization include in response to receiving a request to store data, storing the data in one of a plurality of cache slots of a cache. In one embodiment, the methods further include after storing the data, setting a status of the cache slot as write pending to indicate that the cache slot contains data which needs to be written to a corresponding destination storage device. The methods include determining an eviction type of the cached data based on whether the destination storage device is a local storage device or a remote storage device. In one embodiment, after copying data from the cache slot to the corresponding destination storage device, marking the cache slot with the determined eviction type. In response to receiving another request to store data, evicting at least one of the cache slots based on the eviction type.

Abstract: A system for resolving write pressure includes a primary storage unit, a backup storage unit, and a processor. The primary storage unit comprises a primary storage unit input buffer and a volume storage unit. The backup storage unit comprises a backup storage unit input buffer and a volume backup storage unit. The processor is to: store a first set of input data in the backup storage unit input buffer in the event that the primary storage unit input buffer is unable to store the first set of input data and transfer the first set of input data to the primary storage unit input buffer as space is available after storing data from the primary storage unit input buffer in the volume storage unit.

Abstract: A system for improving backup performance includes an interface, a processor, and a memory. The interface is to receive a volume identifier to backup. The processor is to determine allocation for data of a volume associated with the volume identifier in a plurality of storage tiers to improve backup processing, move data based at least in part on the allocation, and backup data of the volume. The memory is coupled to the processor and configured to provide the processor with instructions.

Abstract: A system for resolving write pressure includes a primary storage unit, a backup storage unit, and a processor. The primary storage unit comprises a primary storage unit input buffer and a volume storage unit. The backup storage unit comprises a backup storage unit input buffer and a volume backup storage unit. The processor is to: store a first set of input data in the backup storage unit input buffer in the event that the primary storage unit input buffer is unable to store the first set of input data and transfer the first set of input data to the primary storage unit input buffer as space is available after storing data from the primary storage unit input buffer in the volume storage unit.

Abstract: Migrating data from an old storage device to a new storage device includes creating new paths to the new storage device, freezing old paths to the old storage device, transferring metadata corresponding to the old storage device to the new storage device, where state information is transferred from the old storage device to the new storage device, and thawing the new paths. Migrating data from an old storage device to a new storage device may also include creating new volumes on the new storage device and transferring data from the old storage device to the new storage device. Migrating data from an old storage device to a new storage device may also include dismantling the old paths.