The disclosure herein describes automating runbook operations associated with an application within an application host on an application platform. A runbook definition associated with the application is accessed by a processor, wherein the runbook definition includes trigger events and runbook operations associated with the trigger events. A runbook operator is executed on the application platform based on the accessed runbook definition and a runbook sidecar container is added to the application host by the runbook operator, wherein the runbook operator is enabled to perform the runbook operations within the application host via the runbook sidecar container. Based on detecting a trigger event, a runbook operation associated with the detected trigger event is performed by the runbook operator, via the runbook sidecar container, whereby the application is maintained based on performance of the runbook operations from within the application host.

The present disclosure relates to a method, device and computer program product for executing a job in an application system. Here, the application system comprises a first processing device and a second processing device, and a first response speed of the first processing device being lower than a second response speed of the second processing device. In a method, a job request is received from a user of the application system, the job request specifying that the job is to be executed in the application system; a job type of the job is determined, the job type describing a requirement of the user on a response speed for executing the job; a target processing device is selected from the first processing device and the second processing device in accordance with determining that the job type relates to a high response speed; and the job is assigned to the selected target processing device, so that the job is executed by the target processing device. By means of the above method, a processing device for processing a job is selected based on the type of the job, and further processing devices in the application system may be dispatched more effectively. Furthermore, there is provided a corresponding device and computer program product.

A data storage management approach is disclosed that performs backup operations flexibly, based on a dynamic scheme of monitoring block changes occurring in production data. The illustrative system monitors block changes based on certain block-change thresholds and triggers block-level backups of the changed blocks when a threshold is passed. Block changes may be monitored in reference to particular files based on a reverse lookup mechanism. The illustrative system also collects and stores historical information on block changes, which may be used for reporting and predictive analysis.

A command requesting creation of a backup file and issued by a client-side deduplication library is received. Upon creating the file, a first flag is set on the file indicating that the file should be automatically retention locked after a cooling off period has elapsed. During the cooling off period, a command requesting that the file be opened for writes is received. The first flag is cleared to exclude the file from being automatically retention locked after the cooling off period has elapsed. A second flag is set on the file indicating that writes to the file are in progress. A command requesting that the file be closed, the writes to the backup file thereby being complete, is received. The second flag is cleared. The first flag is reset to allow the file to be automatically retention locked after the cooling off period has elapsed.

Certain embodiments described herein relate to an improved synthetic full backup image generation system. In some embodiments, one or more components in an information management system can identify a file-server-created backup copy in a particular backup format of a plurality of backup formats, determine structure information associated with the particular backup format, and generate a synthetic full backup copy according to the structure information, where the synthetic full backup copy is also in the particular backup format identical to that of the file-server-created backup copy.

A method, apparatus, and system determines an optimal storage configuration of storing backup data. The method may include receiving a request from a client device for determining an optimal storage configuration for storing backup data of a client. The method may include determining a cloud utilization pattern of the backup data based on prior access activities and determining a first suitability score for the first storage class based on the cloud utilization pattern. The method may include, for each of the storage classes of the first storage provider, determining a suitability score for the corresponding storage class if the backup data were stored in the corresponding storage class. The method may include transmitting to the client device a recommendation of a second storage class of the first storage provider having a suitability score higher than the first suitability score based on the suitability score to reduce cloud resources usage.

Embodiments described herein are generally directed to techniques for avoiding or mitigating shared-state damage during a split-brain condition in a distributed network of compute nodes. According to an example, a number, N, of nodes within the distributed computing system is determined. During normal operation of the distributed computing system, a unified state is maintained by synchronizing shared state information. The nodes are ordered by increasing importance to an application from 1 to N. A quora value, q.sub.n, is assigned to each of the nodes in accordance with the ordering, where q.sub.1=1 and each subsequent quora value, q.sub.n+1, is a sum of all prior quora values, q.sub.1 to q.sub.n, plus either 1 or a current value of n. These quora values may then be used to determine membership in the dominant or a yielding set to facilitate recovery from the split-brain condition by performing pessimistic or optimistic mitigation actions.

A backup entity and a method for backing up a disk volume of a production device are provided. The backup entity is configured to: create a first backup image of the disk volume, in a backup repository. Further, the backup entity is configured to obtain a first indication from the production device, wherein the first indication is indicative of a first operation to be performed by the production device on the disk volume. The backup entity is further configured to perform the first operation on the first backup image, to obtain a second backup image in the backup repository. According to the application, a solution to mimic an operation that changes data of a production storage, in a backup system, is provided, which can reduce the amount of data sent from the production storage to the backup system and thus reduce a backup window.

Disclosed herein are systems and method for determining data storage insurance policies. In an exemplary implementation, a method comprises receiving a request to add a data storage insurance policy to a plurality of data files. The method comprises extracting data file attributes and determining a data recovery score for each respective data file based on a uniqueness, criticality, and/or importance of the respective data file. The method comprises determining a hardware score for each of a plurality of performance tiers comprising at least one storage server, based on an available capacity, a performance cost, and/or data recovery scores of data files currently stored at each of the plurality of performance tiers. The method comprises selecting and executing a data storage insurance policy for the respective data file based on a plurality of data recovery rules and/or the comparison of the data recovery score and the hardware score.

According to certain disclosed techniques, tolerance time lengths respectively associated with backup sessions are acquired, wherein a tolerance time length represents the length of time in which data loss is tolerated during a failure of a source storage device associated with a backup session of the plurality of backup sessions. A backup period for performing the backup sessions is determined based on the tolerance time lengths. The backup period is divided into time slices based on a predetermined time interval. At least one time slice is allocated to the backup session based on the tolerance time length. Accordingly, it is possible to ensure that corresponding time slices allocated for each backup session are distributed as evenly as possible throughout the time of day, thus ensuring load balancing of the backup system.