Abstract: A method for responding to access requests, the method may include (a) detecting, by a controller of a local storage system (LSS), a read pattern that (i) is associated with a requestor that is in communication with the LSS, and (ii) is estimated to comprise future read requests that are aimed to a remote part of a file system entity (FSE) that is stored at a remote storage system (RSS); wherein there is a latency difference between a remote latency associated with the remote part of the FSE and a LSS latency that is associated with the requestor; and (b) performing a prefetch process of remote sub-parts of the remote part of the FSE in order to support the read pattern while maintaining a desired latency.

Abstract: A method for snapshot reversion, the method may include initializing a recovery of a storage system, from a failure that stopped a replication of a failed replication snapshot to an other storage system; wherein the other storage system reverted to an older snapshot not stored in the storage system; and reverting to the older snapshot, by the storage system using older snapshot metadata and data received from the storage system; wherein the older snapshot data may include a non-existing indication for a snapshot segment that existed in a snapshot that followed the older snapshot and not exists at the older snapshot, and wherein the data may include one or more older snapshot segments; wherein the reverting to the older snapshot is executed without undoing changes that were made since the older snapshot.

Abstract: A method for generating a reconstructed version of a filesystem entity, the method may include (i) generating fallback retrieval metadata for a reconstructed version segment, when the reconstructed version segment is (a) associated with a corresponding intermediate version segment, and (b) the corresponding intermediate version segment is preceded by a corresponding most updated segment that does not exceed a fallback version of the filesystem entity; wherein the reconstructed version segment, the corresponding intermediate version segment and the corresponding most updated segment that does not exceed a fallback version have a same address range; (ii) generating a non-existing indicator for the reconstructed version segment, when the reconstructed version segment is (a) associated with the corresponding intermediate version segment, and (b) the corresponding intermediate version segment is not preceded by any corresponding most updated segment that does not exceed the fallback version; and (iii) maintaining

Abstract: A method for snapshot reversion, the method may include initializing a recovery of a storage system, from a failure that stopped a replication of a failed replication snapshot to an other storage system; wherein the other storage system reverted to an older snapshot not stored in the storage system; and reverting to the older snapshot, by the storage system using older snapshot metadata and data received from the storage system; wherein the older snapshot data may include a non-existing indication for a snapshot segment that existed in a snapshot that followed the older snapshot and not exists at the older snapshot, and wherein the data may include one or more older snapshot segments; wherein the reverting to the older snapshot is executed without undoing changes that were made since the older snapshot.

Abstract: A method for generating a reconstructed version of a filesystem entity, the method may include (i) generating fallback retrieval metadata for a reconstructed version segment, when the reconstructed version segment is (a) associated with a corresponding intermediate version segment, and (b) the corresponding intermediate version segment is preceded by a corresponding most updated segment that does not exceed a fallback version of the filesystem entity; wherein the reconstructed version segment, the corresponding intermediate version segment and the corresponding most updated segment that does not exceed a fallback version have a same address range; (ii) generating a non-existing indicator for the reconstructed version segment, when the reconstructed version segment is (a) associated with the corresponding intermediate version segment, and (b) the corresponding intermediate version segment is not preceded by any corresponding most updated segment that does not exceed the fallback version; and (iii) maintaining

Abstract: A system and method for managing a storage system may include recording, in a cache memory, data related to user writes to the storage system; setting a time in a next consistency point (NCP) object with a value greater than the current time; and maintaining a first counter related to the number of user writes recorded in the cache memory and that occurred before the time included in the NCP object and after a time included in a consistency point (CP) object; maintaining a second counter related to the number of user writes that were stored in a persistent storage system and that occurred before the time in the NCP object and after a time in the CP object. A system and method for managing a storage system may include initializing the storage system to a consistent state based on the time included in the CP object.

Abstract: A system and method for managing a storage system may include recording, in a cache memory, data related to user writes to the storage system; setting a time in a next consistency point (NCP) object with a value greater than the current time; and maintaining a first counter related to the number of user writes recorded in the cache memory and that occurred before the time included in the NCP object and after a time included in a consistency point (CP) object; maintaining a second counter related to the number of user writes that were stored in a persistent storage system and that occurred before the time in the NCP object and after a time in the CP object. A system and method for managing a storage system may include initializing the storage system to a consistent state based on the time included in the CP object.