Abstract: Example embodiments of the present invention provide a method, a system, and a computer program product for managing tasks in a system. The method comprises running a first task on a system, wherein the first task has a first priority of execution time and the execution of which first task locks a resource on the system, and running a second task on the system, wherein the second task has a second priority of execution time earlier than the first priority of execution time of the first task and the execution of which second task requires the resource on the system locked by the first task. The system then may promote the first task having the later first priority of execution time to a new priority of execution time at least as early as the second priority of execution time of the second task and resume execution of the first task having the later first priority of execution time.

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: A system, computer program product, and computer-executable method of providing a layout-independent cryptographic stamp of a distributed data set from a data storage system, the system, computer program product, and computer-executable method comprising receiving a request for a cryptographic stamp of the distributed data set, creating a hash of each slice of the distributed data set, and using each hash from each slice of the distribute data set to create the cryptographic stamp of the distributed data set.

Abstract: Described embodiments provide systems and methods for operating a storage system wherein an online consistent system checkpoint is generated. The checkpoint contains a point in time image of a system and is used for providing recovery of the system to a known good state. In one embodiment the checkpoint includes volume configuration data, logical volume space, a plurality of layers of metadata, and physical data storage.

Abstract: An apparatus comprises a storage system having storage devices and an associated storage controller. In conjunction with initiation of a checkpoint, the storage controller sets a checkpoint started flag for the checkpoint, marks user data pages and metadata pages for write operations already entered in a write journal of the storage system as of the setting of the checkpoint started flag as checkpoint pages, and marks user data pages and metadata pages for new write operations entered in the write journal after the setting of the checkpoint started flag as non-checkpoint pages by altering information used to generate signatures for respective ones of the metadata pages. Metadata pages characterizing the same user data pages subject to write operations at different times thereby have different signatures depending on whether or not the checkpoint started flag was set when its corresponding write operation was entered in the write journal.

Abstract: Techniques for processing I/O operations may include: receiving, an I/O operation including a tag value denoting a process of a database application that issued the I/O operation; determining, in accordance with the tag value, whether the I/O operation is directed to a data file storing content of a database or a log file of recorded operations of the database; and responsive to determining the I/O operation is directed to a data file storing content of the database, performing processing including: determining a current configuration setting of the database that indicates whether the database is configured for use with the database application as an in-memory database; and determining, in accordance with current configuration setting of the database, a first service level objective for the I/O operation, wherein the first service level objective for the I/O operation is a default service level objective or a revised service level objective.

Abstract: An aspect includes generating a checkpoint for a storage system containing an image for a point in time. An aspect also includes storing, in a reserved area, volume configuration data corresponding to volumes for the point in time, layers of metadata and physical data for the point in time. An aspect further includes creating consistent snapshots for the volumes, destaging a control module journal and persisting a hash tree and dirty tree metadata, destaging a code cache, dumping hash metadata and physical layout metadata to a separate location in the storage and enabling new metadata updates to a default location. An aspect also includes redirecting new data and metadata IOS to stripes reserved during preparation of the separate location relating to the checkpoint and protecting checkpointed data and metadata, and generating a consistent checkpoint copy of a management module repository in the reserved area of storage.

Abstract: An aspect includes determining, in response to an efficiency indicator associated with a destination disk array of a plurality of destination disk arrays, to relocate at least a portion of data currently on a source Logical Unit (LUN) of a source disk array of a plurality of source disk arrays to the destination disk array. The efficiency indicator represents an amount of data on the source LUN that also resides on the destination disk array. The destination disk array supports deduplication. An aspect also includes evaluating multiple destination LUNs of the destination disk array to relocate the data to based on the efficiency indicator and at least one capacity-based factor corresponding to the multiple destination LUNs, selecting one of the multiple destination LUNs to relocate the data based on results of the evaluating, and relocating the data from the source LUN to the selected one of the multiple destination LUNs.

Abstract: Determining an expected compression rate for a prospective process in a federated system includes obtaining compression rate data for existing processes in the federated system, compiling the compression rate data into a plurality of entries in a process name table according to process identifier, client, and industry, determining a specific entry in the process name table for an existing process that most closely matches the prospective process, and determining an expected compression rate of the prospective process based on the compression rate data for the specific entry. Compression rate data may be provided by a driver at host systems that sends compression rate information to a central repository. The central repository may be provided by a host system at a data center of the federated system. The compression rate data may use a sliding average that weighs the data more heavily to favor more recent data.

Abstract: A system, computer program product, and computer-executable method of scheduling replication on a data storage system, the system, the computer program product, and computer-executable method including receiving a request to replicate a portion of data stored on the data storage system, dividing the portion of data into a plurality of portions, scheduling replication of each of the plurality of portions, and replicating each of the plurality of portions.

Abstract: An information handling system includes a server and a storage array. The server includes a memory buffer that stores data for an operating system executed within the server. The server detects that a shut down of the server has been initiated, and provides a signal indicating that the shut down has been initiated. The storage array receives the signal from the server, and increases a service level objective of write commands from the server in response to the signal being received.

Abstract: An apparatus in one embodiment comprises at least one processing device comprising a processor coupled to a memory. The processing device is configured to capture metadata from a metadata area of a storage system for checkpointing, and to store the captured metadata as checkpointed metadata in a user data area of the storage system in association with mapping information relating portions of the checkpointed metadata to particular storage locations in the user data area. The processing device in some embodiments is implemented within the storage system, and may comprise a storage controller of the storage system. The mapping information illustratively comprises a plurality of page location arrays each having a plurality of entries specifying respective locations of checkpointed metadata pages in the user data area.

Abstract: Example embodiments relate to a method, a system, and a computer program product for load balancing for port selection. The method includes determining a processing load for each storage port in a plurality of storage ports having variable processing power and calculating a delay characteristic for each storage port of the plurality of storage ports according to its processing load. A command then may be sent to a selected storage port of the plurality of storage ports according to the delay characteristics and a policy.

Abstract: Example embodiments of the present invention provide a method, a system, and a computer program product for managing tasks in a system. The method comprises running a first task on a system, wherein the first task has a first priority of execution time and the execution of which first task locks a resource on the system, and running a second task on the system, wherein the second task has a second priority of execution time earlier than the first priority of execution time of the first task and the execution of which second task requires the resource on the system locked by the first task. The system then may promote the first task having the later first priority of execution time to a new priority of execution time at least as early as the second priority of execution time of the second task and resume execution of the first task having the later first priority of execution time.

Abstract: Systems and methods for replicating data are disclosed. Data stored in a compressed form on a source storage array or device can be read and transmitted to a destination storage array or device. The replication of data is achieved without having to decompress the data.

Abstract: Described embodiments provide systems and methods for operating a storage system wherein an online consistent system checkpoint is generated. The checkpoint contains a point in time image of a system and is used for providing recovery of the system to a known good state. In one embodiment the checkpoint includes volume configuration data, logical volume space, a plurality of layers of metadata, and physical data storage.

Abstract: Example embodiments of the present invention provide a method, a system, and a computer program product for managing tasks in a system. The method comprises running a first task on a system, wherein the first task has a first priority of execution time and the execution of which first task locks a resource on the system, and running a second task on the system, wherein the second task has a second priority of execution time earlier than the first priority of execution time of the first task and the execution of which second task requires the resource on the system locked by the first task. The system then may promote the first task having the later first priority of execution time to a new priority of execution time at least as early as the second priority of execution time of the second task and resume execution of the first task having the later first priority of execution time.

Abstract: Techniques for processing I/O operations may include: receiving, an I/O operation including a tag value denoting a process of a database application that issued the I/O operation; determining, in accordance with the tag value, whether the I/O operation is directed to a data file storing content of a database or a log file of recorded operations of the database; and responsive to determining the I/O operation is directed to a data file storing content of the database, performing processing including: determining a current configuration setting of the database that indicates whether the database is configured for use with the database application as an in-memory database; and determining, in accordance with current configuration setting of the database, a first service level objective for the I/O operation, wherein the first service level objective for the I/O operation is a default service level objective or a revised service level objective.

Abstract: An information handling system includes a server and a storage array. The server includes a memory buffer that stores data for an operating system executed within the server. The server detects that a shut down of the server has been initiated, and provides a signal indicating that the shut down has been initiated. The storage array receives the signal from the server, and increases a service level objective of write commands from the server in response to the signal being received.

Abstract: Example embodiments of the present invention relate to methods, systems, and a computer program product for detecting and avoiding storage array performance degradation. The method includes anticipating an unpredictable performance state of a storage device in a storage array that degrades storage array functionality according to a performance profile for a storage device type of the storage device. In response, performance of the storage array may be adjusted to avoid the storage device entering the unpredictable performance state.