Abstract: Embodiments are directed to managing data in a file system that includes a plurality of storage nodes and a plurality of storage volumes in a cloud computing environment. Metrics associated with each storage volume may be monitored. In response to the metrics exceeding a threshold value, performing further actions, including: determining storage volumes that are unhealthy based on the metrics that exceed the threshold value; updating metadata associated with the storage volumes to indicate that the storage volumes are unhealthy; decoupling the unhealthy storage volumes from storage nodes coupled to the unhealthy storage volumes; determining replacement storage volumes based on the metadata associated with the unhealthy storage volumes; updating other metadata associated with the replacement storage volumes to indicate that the replacement storage volumes are healthy storage volumes; and coupling the healthy storage volumes with the storage nodes that were coupled to the unhealthy storage volumes.

Abstract: Embodiments are directed to managing data in a file system that includes storage nodes and storage volumes in a cloud computing environment (CCE). A backup job may be executed to perform further actions, including: providing a backup identifier that is associated with the backup job; determining the storage nodes based on the file system and the CCE; disabling the file system by disabling the storage nodes, wherein each disabled storage node is associated with a shutdown timestamp; determining storage volumes associated with each disabled storage node; and generating storage images that archive a copy of information from the storage volumes; associating the storage images with the backup identifier; confirming that the file system is consistent based on an absence of file system activity occurring subsequent to each shutdown timestamp; and enabling the file system by enabling the storage nodes.

Abstract: Embodiments are directed to managing data in a file system that includes a plurality of storage nodes and a plurality of storage volumes in a cloud computing environment. Metrics associated with each storage volume may be monitored. In response to the metrics exceeding a threshold value, performing further actions, including: determining storage volumes that are unhealthy based on the metrics that exceed the threshold value; updating metadata associated with the storage volumes to indicate that the storage volumes are unhealthy; decoupling the unhealthy storage volumes from storage nodes coupled to the unhealthy storage volumes; determining replacement storage volumes based on the metadata associated with the unhealthy storage volumes; updating other metadata associated with the replacement storage volumes to indicate that the replacement storage volumes are healthy storage volumes; and coupling the healthy storage volumes with the storage nodes that were coupled to the unhealthy storage volumes.

Abstract: Embodiments are directed to managing data in a file system that includes storage nodes and storage volumes in a cloud computing environment (CCE). A backup job may be executed to perform further actions, including: providing a backup identifier that is associated with the backup job; determining the storage nodes based on the file system and the CCE; disabling the file system by disabling the storage nodes, wherein each disabled storage node is associated with a shutdown timestamp; determining storage volumes associated with each disabled storage node; and generating storage images that archive a copy of information from the storage volumes; associating the storage images with the backup identifier; confirming that the file system is consistent based on an absence of file system activity occurring subsequent to each shutdown timestamp; and enabling the file system by enabling the storage nodes.

Abstract: Embodiments are directed to a file system engine that provides a file system that includes a plurality of blocks on a file storage tier with portion of the blocks associated with a cache storage tier. A cache engine provides heat extents that include a heat score and a run length value such that the heat extents are represent activities associated with the blocks. Heat extents associated with file system activities are determined based on a position of the blocks that corresponds with the run length values of the heat extents and sectors on the file storage tier. Heat scores associated with the heat extents may be modified based on the activities and distribution models to conform the heat extents with the distribution models. Blocks associated with heat scores that are less than a threshold value provided by the distribution models may be disassociated from the cache storage tier.

Abstract: Embodiments are directed to managing data in a file system that includes storage nodes and storage volumes in a cloud computing environment (CCE). A backup job may be executed to perform further actions, including: providing a backup identifier that is associated with the backup job; determining the storage nodes based on the file system and the CCE; disabling the file system by disabling the storage nodes, wherein each disabled storage node is associated with a shutdown timestamp; determining storage volumes associated with each disabled storage node; and generating storage images that archive a copy of information from the storage volumes; associating the storage images with the backup identifier; confirming that the file system is consistent based on an absence of file system activity occurring subsequent to each shutdown timestamp; and enabling the file system by enabling the storage nodes.

Abstract: Embodiments are directed to a file system engine that provides a file system that includes a plurality of blocks on a file storage tier with portion of the blocks associated with a cache storage tier. A cache engine provides heat extents that include a heat score and a run length value such that the heat extents are represent activities associated with the blocks. Heat extents associated with file system activities are determined based on a position of the blocks that corresponds with the run length values of the heat extents and sectors on the file storage tier. Heat scores associated with the heat extents may be modified based on the activities and distribution models to conform the heat extents with the distribution models. Blocks associated with heat scores that are less than a threshold value provided by the distribution models may be disassociated from the cache storage tier.

Abstract: Embodiments are directed to a file system engine that provides a file system that includes a plurality of blocks on a file storage tier with portion of the blocks associated with a cache storage tier. A cache engine provides heat extents that include a heat score and a run length value such that the heat extents are represent activities associated with the blocks. Heat extents associated with file system activities are determined based on a position of the blocks that corresponds with the run length values of the heat extents and sectors on the file storage tier. Heat scores associated with the heat extents may be modified based on the activities and distribution models to conform the heat extents with the distribution models. Blocks associated with heat scores that are less than a threshold value provided by the distribution models may be disassociated from the cache storage tier.