Abstract: A method embodiment commences upon identifying an on-premises storage area such as a file or virtual disk that is composed of a set of data blocks. A history of data access patterns over the data blocks is determined by observing accesses to the data blocks over time. When offsite storage is demanded (e.g., such as to a cloud-based storage facility), one or more storage objects are formed such that the blocks in a first one of the one or more storage objects comprise the blocks that have been measured to have the highest access rates (e.g., most recently accessed or most frequently accessed). Metadata that serves as a map is stored with the storage objects. A process or thread can access the storage objects in expectation that the most recently accessed or most frequently accessed blocks will be available in the first ones of the one or more storage objects.

Abstract: Systems, methods, and computer program products for distributed data storage. A spot defragmentation method commences upon receiving an incoming storage I/O command to access a subject logical object that is composed of subject logical data blocks. The method continues by retrieving a block map that characterizes spatial relationships between the subject logical data blocks and instances of respective subject physical data blocks that store the subject logical object on a storage device. During processing of the incoming storage I/O command, the method determines occurrences of, and locations of one or more fragmented physical data blocks. A defragmentation operation is initiated to coalesce the fragmented physical data blocks to another location. The defragmentation operation is initiated before completing the storage I/O command.

Abstract: Systems for distributed data storage. A method embodiment commences upon capturing a history of storage I/O activity over a recent time period. A predictive model is derived from the captured storage I/O activity, and the predictive model is then used for predicting future storage I/O activity. A set of snapshot planning parameters comprising objectives (e.g., to minimize costs or to maximize likelihood completing a snapshot activity by a prescribed time) and/or constraints (e.g., don't wait more than one day to start a snapshot) are applied to the predicted storage I/O characteristics to generate a set of feasible snapshot plans. One of the feasible snapshot plans is selected for scheduling so as to begin the planned snapshot activity at a prescribed time. The snapshot planning parameters are normalized based on the predicted storage I/O characteristics.