Abstract: The present invention relates to a system and method for supporting application resilience. The objective is to engineer fault awareness and recovery capabilities in an application. The system provides a structured, repeatable and comprehensive approach for addressing resilience of IT systems. Further, it proposes a well-defined set of activities and specifies output for each phase which when integrated into regular SDLC will help systematically build resilience into enterprise applications. The system further optimizes the effort involved using a vulnerability based scoring mechanism that provides the right level of engineering needed based on the applications susceptibility to failures and the impact to the customer's business activities.

Abstract: The present invention relates to a system and method for supporting application resilience. The objective is to engineer fault awareness and recovery capabilities in an application. The system provides a structured, repeatable and comprehensive approach for addressing resilience of IT systems. Further, it proposes a well-defined set of activities and specifies output for each phase which when integrated into regular SDLC will help systematically build resilience into enterprise applications. The system further optimizes the effort involved using a vulnerability based scoring mechanism that provides the right level of engineering needed based on the applications susceptibility to failures and the impact to the customer's business activities.

Abstract: In general, a block of data in a data file is stored in a multi-tier storage system. The block of data includes multiple rows and multiple entry values per row, including values for a particular entry. The values of the particular entry in the data block can be used to determine whether to move the data block to a different tier of a multi-tier storage system. The block of data can then either be relocated in a different tier or kept in the current tier.

Abstract: A sliding window policy is implemented to manage database objects. At a first time, a first portion of a database object is allocated to a first tier of a multi-tier storage system. The first portion corresponds to a first specified percentage of the size of the database object at the first time and is selected according to information associated with the database object. The remaining portion of the database object at the first time is allocated to one or more other tiers. At a second (later) time, a second portion of the database object is allocated to the first tier. The second portion corresponds to a second specified percentage of the size of the database object at the second time and is also selected according to information associated with the database object. The remaining portion of the database object at the second time is allocated to the other tier(s).

Abstract: The present disclosure presents a method for managing portions of files in multi-tier storage systems. The method may include identifying a file that is managed by an application and stored in a multi-tier storage system. The method may also include determining how the application stores data in the file by identifying data-management information associated with the application. The method may further include using the data-management information to identify a first portion of the file, identifying a data-placement policy, and implementing the data-placement policy by moving the first portion of the file from a first tier of the multi-tier storage system to a second tier of the multi-tier storage system. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: A sliding window policy is implemented to manage database objects. At a first time, a first portion of a database object is allocated to a first tier of a multi-tier storage system. The first portion corresponds to a first specified percentage of the size of the database object at the first time and is selected according to information associated with the database object. The remaining portion of the database object at the first time is allocated to one or more other tiers. At a second (later) time, a second portion of the database object is allocated to the first tier. The second portion corresponds to a second specified percentage of the size of the database object at the second time and is also selected according to information associated with the database object. The remaining portion of the database object at the second time is allocated to the other tier(s).

Abstract: In general, a block of data in a data file is stored in a multi-tier storage system. The block of data includes multiple rows and multiple entry values per row, including values for a particular entry. The values of the particular entry in the data block can be used to determine whether to move the data block to a different tier of a multi-tier storage system. The block of data can then either be relocated in a different tier or kept in the current tier.