Systems and methods for managing electronic data are disclosed. Various data management operations can be performed based on a metabase formed from metadata. Such metadata can be identified from an index of data interactions generated by a journaling module, and obtained from their associated data objects stored in one or more storage devices. In various embodiments, such processing of the index and storing of the metadata can facilitate, for example, enhanced data management operations, enhanced data identification operations, enhanced storage operations, data classification for organizing and storing the metadata, cataloging of metadata for the stored metadata, and/or user interfaces for managing data. In various embodiments, the metabase can be configured in different ways. For example, the metabase can be stored separately from the data objects so as to allow obtaining of information about the data objects without accessing the data objects or a data structure used by a file system.

A method to generate and maintain always current backup copy of database system with minimum system resource in a very large RDBMS or other database environment. Requiring one life time full backup only and then periodic differential backups unlike periodic full backups in current case. A method to use these backup files to recover to a point in time. Reducing time and resource utilization on very large database backup by applying these methods. This method eliminates the need to take periodic full backup copy on a database.

Methods and systems for improving the performance of a primary system that is running one or more virtual machines and capturing snapshots of the one or more virtual machines over time are described. The performance penalty on the primary system when a hypervisor running the one or more virtual machines is used to capture the snapshots of the one or more virtual machines may be reduced by leveraging storage array snapshots to reduce the amount of time that the hypervisor must freeze virtual disks of the one or more virtual machines. In this case, changed block tracking information for changed data blocks associated with the snapshots may be acquired from the hypervisor and the changed data blocks themselves may be pulled from the storage array snapshots without requiring the hypervisor to keep the virtual disks of the one or more virtual machines in a frozen state.

A system for reducing VM stunting during backup of a set of virtual machines is provided. In some examples, a system comprises processors and a memory storing instructions that, when executed by at least one processor among the processors, cause the system to perform certain operations. Example operations may include running an analytic process to learn resource utilization patterns of a hypervisor system monitoring the set of virtual machines, determining an opportunistic window of reduced resource utilization based on the resource utilization patterns, and scheduling backup for the set of virtual machines during the opportunistic window.

An apparatus comprises at least one processing device that includes a processor coupled to a memory. The processing device is configured to control delivery of input-output (IO) operations from a host device to at least one storage system over selected ones of a plurality of paths through a network, and to detect initiation of a non-disruptive upgrade of the host device. The processing device is further configured to identify, responsive to the detected initiation, one or more of the plurality of paths that will become temporarily unavailable in conjunction with the non-disruptive upgrade, and to modify path selection in the host device to avoid selecting the identified paths for at least a portion of a time period during which the non-disruptive upgrade is in progress. The processing device illustratively comprises at least a portion of the host device, including a multi-path input-output (MPIO) driver that performs at least a portion of the detection, identification and modification.

A method for enhancing speed of incremental backup, a bridge device, and a storage system are provided. The method includes: regarding a predetermined location within the storage system, determining whether a record file exists; in response to the record file existing, determining whether any file needing to be compared exists; in response to said any file needing to be compared existing, comparing said any file needing to be compared with content of the record file to generate at least one comparison result, wherein said at least one comparison result indicates whether a set of attributes of said any file needing to be compared completely exist in the record file; according to said at least one comparison result, determining whether any difference is found; and in response to said any difference being not found, preventing triggering any backup from a source storage device to a target storage device.

Provided are a computer program product, system, and method for establishing a point-in-time copy relationship between source logical addresses and target logical addresses. A point-in-time (PiT) copy establish command specifies a source set comprising a subset of source logical addresses in at least one storage and a target set comprising a subset of target logical addresses in the at least one storage. The source set of source logical addresses are copied to the target set of target logical addresses. The source logical addresses map to source tracks and wherein the target logical addresses map to target tracks. Copy information is generated indicating whether the source logical addresses in the source set have been copied to the target set. Complete is returned to the PiT copy establish command after generating the copy information and before copying all the source logical addresses to the target logical addresses.

A non-volatile static random access memory has an operating mode, a data backup mode and a data restore mode. The non-volatile static random access memory includes a memory cell and a power saving module. The memory cell includes a latch, a set of latch switch units, a set of backup memory units, a set of backup activation units, a backup setting unit and a driving signal transmission unit. The power saving module includes a control switch unit, a backup determination unit and a restore switch unit. When backup data is different from data stored in the latch, a backup driving signal is generated by a node voltage of the backup memory units and outputted to a backup determination unit, which drives the backup setting unit to turn on according to the backup driving signal, so as to change the backup data in the backup memory units and ensure correct backup.

Techniques include receiving a backup request for backing up data on a production VVOL, to which is assigned physical space from storage devices in a first storage tier. When the production VVOL and a snapshot VVOL exist, and a write request is received to a data block on the production VVOL that is shared between the production VVOL and the snapshot VVOL, then the techniques include capturing a snapshot of the production VVOL by redirecting the write request to newly allocated space on the production VVOL, writing new data to the newly allocated space, and storing metadata referring to the original block(s) on the production VVOL. Based on an IO workload threshold, the techniques include copying, in a background process, the original version of the modified block from the production VVOL to a snapshot VVOL, to which is assigned physical storage space from storage devices in a second storage tier.

In accordance with implementations of the present disclosure, a backup of live data received by a data forwarder is generated at the data forwarder while the live data is provided to a real-time data pipeline for forwarding from the data forwarder. A first portion of the live data is recovered from the backup to a stale data pipeline of the data forwarder. A request to forward the live data to a destination node is received by the data forwarder. In response to the request data is forwarded to the destination node, where the first portion of the live data from the stale data pipeline is added to a second portion of the live data from the real-time data pipeline in the response based on determining headroom remains to reach an amount of the data identified to include in the response.