Techniques described herein relate to a method for generating backups of virtual machines. The method may include, in response to identifying a backup generation event associated with virtual machines: obtaining, by a backup agent, virtual machine metadata associated with the virtual machines; identifying groups of virtual machines based on the virtual machine metadata; provisioning resources to generate backups of the virtual machines based on the groups of virtual machines; and generating a backup of the virtual machines based on the groups of virtual machines using the provisioned resources associated with the groups of virtual machines.

Processing I/O operations may include: receiving, at a data storage system, an I/O operation from a host, wherein the I/O operation is directed to a logical address and includes an I/O tag used in connection with performing data reduction processing for first data stored at the logical address; and performing processing to back up a data set including the first data stored at the logical address. The processing may include: sending, from the data storage system to a backup application, the data set and hints regarding the first data set, wherein the hints include a first hint determined in accordance with the I/O tag from the host; performing, in accordance with the hints, data reduction processing of the data set to generate a second data set; and storing the second data set on one or more backup storage devices.

Techniques described herein relate to a method for generating backups of assets. The method may include identifying, by a backup agent, a backup generation event associated with an asset; in response to identifying the backup generation event: obtaining change information associated with the asset, and the change information includes at least one change list; generating an asset backup using the at least one change list, in which the asset backup includes asset backup data, asset backup metadata, and historical metadata; and storing the asset backup in a backup storage.

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.

A method of fault-tolerant process control includes providing a network process control system in an industrial processing facility (IPF) including a plant-wide network coupling a server to computing platforms each including computing hardware and memory hosting a software application for simultaneously supporting a process controller and another process controller or an I/O gateway. The computing platforms are coupled together by a private path redundancy network for providing a hardware resource pool. At least some of the computing platforms are directly coupled by an I/O mesh network to a plurality of I/O devices to field devices that are coupled to processing equipment. Upon detecting at least one failing device in the hardware resource pool, over the private path redundancy network a backup is placed into service for the failing device from the another process controller or I/O gateway that is at another of the computing platforms in the hardware resource pool.

Disclosed herein are systems and methods for enabling self-notarization in a data backup. In one aspects, a method may comprise generating the data backup at a computing device. The method may comprise calculating a checksum of the data backup. The method may comprise adding a self-notarization script to the data backup. The self-notarization script may be configured to automatically trigger without intervention by an external notarization system, in response to a pre-determined backup storage event, and in response to triggering, notarize and send the checksum to a distributed registry. The method may comprise sending the data backup comprising the self-notarization script to a backup storage device.

A file data access method and apparatus, and a medium. The method includes: when a file copy instruction is received, creating a backup file; recording, in metadata of an original file, identification information of the backup file, and recording, in metadata of the backup file, identification information of the original file; when a read instruction for a first target file is received, determining whether there is a data object corresponding to the first target file; if YES, reading the data object; and if NO, determining a first target original file associated with the first target file according to identification information recorded in metadata of the first target file, and reading a data object of the first target original file. During data backup, an original file may be backed up by merely recording, in metadata, identification information of an associated file, without copying a data object.

One example method includes performing delta operations to protect data. Each delta generated by a data protection operation includes data. The deltas are stored in a delta queue, when moving a current replica to another point in time represented by the selected delta in the delta queue, the deltas are processed so that all relevant data can be applied in a batch. This ensures that when the same extents are represented in multiple deltas, only the oldest version is applied to the replica volume to move the current replica to the selected point in time.

A method, computer program product, and computing system for receiving a selection of one or more secure snapshots to remove from a storage system. A snapshot deletion key may be received from the storage system. The selection of the one or more secure snapshots and the snapshot deletion key may be provided to a storage system support service. A snapshot deletion response may be received from the storage system support service. The snapshot deletion response and the selection of the one or more secure snapshots may be authenticated via the storage system. In response to authenticating the snapshot deletion response and the selection of the one or more secure snapshots, the one or more secure snapshots may be unlocked for deletion.

A production host for hosting applications includes a persistent storage and a production agent. The persistent storage stores application data of the applications. The production agent obtains a backup analysis request for an application executing on the production host; in response to obtaining the backup analysis request: obtains an identity of the application; identifies backups in a backup storage, wherein the identified backups are associated with the identity of the application; performs a backup policy compliance analysis of the identified backups to generate a backup protection map for the application.