Hewlett Packard Enterprise Development LP

Sijesh Thondapilly Balakrishnan

Aswin Jayaraman

Sankar Ramasamy

Naveen Kumar Selvarajan

Alastair Michael Slater

Arun Krishna Pillai

In some examples, a system receives a request to recover a program. The system accesses metadata associated with a recovery copy of information for the program, and determines, based on the metadata, a compatibility of a storage arrangement of data in the recovery copy with the program. The system determines whether to fully recover the program using the recovery copy or to partially recover the program based on the determined compatibility.

Program recovery

Example implementations relate to backup operations in a storage system. An example includes a medium storing instructions to: detect a trigger event to initiate a backup restoration of a data entity at a local storage system; determine a user preference between a speed priority and a cost priority; based at least on the determined user preference, select between: an indirect restoration option in which a first portion of the backup data stored on the remote storage system is combined with a second portion of backup data stored on a gateway device to restore the data entity at the local storage system; and a direct restoration option in which the backup data stored on the remote storage system is restored at the local storage system without being combined with other backup data; and restore, using the selected first restoration option, the data entity at the local storage system.

Backup recovery from remote storage

Examples described herein relate to a data protection policy management system (DPPMS) for tuning a data protection policy in events of failures. The DPPMS may detect a failure associated with an application that is protected via the data protection policy that includes settings corresponding to parameters comprising one or more of copy tiers, a data retention interval and a recovery point objective (RPO) for the copy tiers. The DPPMS may determine a type of the failure associated with the application. Further, the DPPMS may select, based on the type of the failure, at least one parameter of the parameters to be tuned in response to detection of the failure. Moreover, the DPPMS may tune the settings corresponding to the at least one selected parameter to adapt the data protection policy.

Tuning data protection policy after failures

Examples described herein relate to a method for managing data management policies of resources. An example includes detecting a movement of a resource from a first resource group protected by a first data management policy to a second resource group protected by a second data management policy. Further, in response to detection of the movement of the resource, a data management policy of the second resource group may be upgraded if first data management policy provides an enhanced level of copy data management over the second data management policy.

Managing data management policies of resources

Example implementations relate to determining a storage utilization attributable to object data stored in deduplicated form. The storage utilization attributable to the object data may be determined from an amount of object data not shared with other objects of the deduplication store and a portion of an amount of object data shared with other objects of the deduplication store. It is determined whether the storage utilization results in exceeding a storage threshold of a storage tier to which the object data is assigned. Where the storage utilization is determined to exceed the storage threshold, the object data may be reassigned to a different storage tier, or data of another object may be removed from the storage tier.

Cost-aware storage allocation of deduplicated objects

In some examples, data integrity verification may include obtaining, from an application for which data is stored in a primary storage volume, an identification of data blocks of the primary storage volume that are stored for the application in a snapshot storage volume that represents a snapshot of data stored in the primary storage volume. The identification may include references to locations of the data blocks in the primary storage volume. Using physical extent mappings and volume block addressing, the identified locations of the data blocks in the primary storage volume may be translated to locations of snapshot storage volume blocks of the snapshot storage volume. Based on the snapshot storage volume blocks that are read from the snapshot storage volume, integrity of corresponding backup copy blocks stored in a backup copy for backup of the primary storage volume may be verified.

Growing community of inventors

Bengaluru, India

Sijesh Thondapilly Balakrishnan