Abstract: One or more aspects of the present disclosure relate to autonomous write fencing for backup power. In embodiments, an input/output (IO) workload is received at a storage array. Additionally, one or more IO write requests in the IO workload are cached based on a charge level of a backup power supply of the storage array. Further, the cached IO write requests are processed.

Abstract: A profile of characteristics of a normal snapshot of a storage object is computed from previous snapshots of the storage object. Characteristics of a new snapshot are compared with the characteristics in the profile to identify an anomaly indicative of a malicious attack. The characteristics include percent data changed between consecutive snapshots, write LBA dispersion, write data reducibility, number and size of writes, write workload profile, and write content profile. The new snapshot is only vaulted or air-gapped if all its characteristics are within ranges defined by the profile.

Abstract: One or more aspects of the present disclosure relate to autonomous write fencing for backup power. In embodiments, an input/output (IO) workload is received at a storage array. Additionally, one or more IO write requests in the IO workload are cached based on a charge level of a backup power supply of the storage array. Further, the cached IO write requests are processed.

Abstract: A profile of characteristics of a normal snapshot of a storage object is computed from previous snapshots of the storage object. Characteristics of a new snapshot are compared with the characteristics in the profile to identify an anomaly indicative of a malicious attack. The characteristics include percent data changed between consecutive snapshots, write LBA dispersion, write data reducibility, number and size of writes, write workload profile, and write content profile. The new snapshot is only vaulted or air-gapped if all its characteristics are within ranges defined by the profile.

Abstract: A primary storage system appends a red-hot data indicator to each track of data transmitted on a remote data facility during an initial synchronization state. The red-hot data indicator indicates, on a track-by-track basis, whether the data associated with that track should be stored as compressed or uncompressed data by the backup storage system. The red-hot data indicator may be obtained from the primary storage system's extent-based red-hot data map. If the red-hot data indicator indicates that the track should remain uncompressed, or if the track is locally identified as red-hot data, the backup storage system stores the track as uncompressed data. If the red-hot data indicator indicates that the track should be compressed, the backup storage system compresses the track and stores the track as compressed data. After the initial synchronization process has completed, red-hot data indicators are no longer appended to tracks by the primary storage system.

Abstract: Described are techniques user to determine expected service levels. A first set of one or more data portions are selected from one or more devices forming a first device set. The first set of data portions are stored on physical storage of a physical device set of one or more physical devices having an unknown service level expectation. I/O operations directed to the first set of data portions are received and serviced for a time period. First information is collected that characterizes performance of the physical device set during the time period. In accordance with the first information and using an adaptive learning technique, a first service level expectation for servicing I/Os directed to the physical device set is determined.