18 results about "Recovery point objective" patented technology

An illustrative data storage management system comprises a management database that stores administrative preferences and system configurations, as well as results and / or statistics of completed secondary storage operations, i.e., information needed by the system to protect customers' data and to track and recover the protected data, including secondary copies such as backup copies, archive copies, etc. The disclosed data storage management system is configured to protect its own system data subject to a very aggressive (short) Recovery Point Objective (RPO), by using an innovative infrastructure that enables the system's storage manager to fail over to any number of other failover destination storage managers, each one comprising a destination management database. An illustrative database granularly tracks whether each and every transaction log file has been successfully applied to each and every destination management database to synchronize with the source management database.

In one example, the present storage solution provides an order of operations of a computer-implemented method that includes establishing bi-directional synchronous replication between one or more members of a first consistency group (CG1) of a primary storage site and one or more members of a second consistency group (CG2) of a secondary storage site with each storage site having read / write access while maintaining zero recovery point objective (RPO) and Zero recovery time objective (RTO). The method includes initiating a non-disruptive planned failover to change a role for the secondary storage site and change a role for the primary storage site while maintaining in sync status of the bi-directional synchronous replication between the one or more members of the CG1 of the primary storage site and the one or more members of the CG2 of a secondary storage site, and while maintaining zero data loss protection.

The invention provides a dynamic data-backup scheduling system. The system includes a memory storing one or more processor-executable routines and a processor communicatively coupled to the memory. The processor is configured to execute one or more processor-executable routines to determine a dynamic backup schedule for one or more computing machines based upon data change patterns of the respective computing machines. The processor is further configured to access user inputs corresponding to data backup for the one or more computing machines. The user inputs comprise at least one of a tolerable data loss threshold, critical data type, file sensitivity data, and exceptions data time period information. The processor is further configured to create one or more service level agreement (SLA) configurations for data backup based on the user inputs. The processor is further configured to access historical data corresponding to one or more data backup cycles of the one or more computing machines. The historical data comprises one or more of time series changes, the addition and / or change of data information for pre-determined data sets, and corresponding file metadata of the data sets. The processor is further configured to implement one of the active and passive modes of data backup using the user inputs and the historical data. The processor is further configured to trigger a backup job for one or more computing machines based on a comparison between the SLA configurations and dynamic information received about data addition and / or data change of the computing machines in the active mode. The processor is further configured to trigger a backup job for one or more computing machines based on a comparison between the SLA configurations and historical time series change and / or addition of data of the computing machines in the passive mode.

Techniques can include: establishing an asynchronous replication configuration for a replication session of a source volume group VG1 and a target volume group VG2; and performing processing to transition the replication session to a low RPO (recovery point objective) replication mode comprising: setting the replication session to an alternative asynchronous replication (AAR) mode; transitioning the replication session to a hybrid mode; creating a first snapset of snapshots of source volumes of VG1; replicating each snapshot of the first snapset from a source to a target system in either the low RPO replication mode or the AAR mode based on an associated member level asynchronous replication mode corresponding to said each snapshot; and constructing a second snapset of snapshots of target volumes of VG2, wherein each snapshot in the second snapset denotes a same point in time copy as a corresponding snapshot in the first snapset.

Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I / O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).

For reliability, availability, and serviceability (RAS) of a database, here are novel performance optimization rules that generate a configuration of a new database or an improved configuration of an existing database. These rules perform a service level agreement (SLA) assessment to detect which database architecture options are needed. The rules recommend improvements to the database's current architecture so that recovery time objectives (RTO) and recovery point objectives (RPO) can be achieved by non-expert technicians. The rules analyze database diagnostics from health monitoring, diagnostic logs, persistent and network storage statistics, database performance statistics, and operating system (OS) statistics. The rules may analyze a database configuration that contains an interactively completed questionnaire or a diagnostic report generated by database infrastructure. The rules can be used speculatively to predict the RAS performance characteristics of an unimplemented configuration or used remedially to generate suggestions for improving RAS performance of a deployed configuration.

The invention relates to a method, equipment and a product for adjusting a recovery point target. The method includes determining a total replication bandwidth and a replication link bandwidth, where the total replication bandwidth indicates a sum of replication bandwidths for the plurality of replication sessions and the replication link bandwidth indicates a maximum bandwidth for the replication link. The method further includes, in response to the total replication bandwidth being greater than the replication link bandwidth, increasing a recovery point target of the replication link, where the recovery point target indicates a maximum data loss time range. The method further includes reducing a recovery point target of the copy link in response to the total copy bandwidth being less than the copy link bandwidth. By means of the method for dynamically adjusting and recovering the point target, the copy link bandwidth can be utilized at the maximum efficiency, and therefore the copy efficiency is improved.

In one example, a computer-implemented method includes establishing bi-directional synchronous replication between one or more members of a first consistency group (CG1) of a primary storage site and one or more members of a second consistency group (CG2) of a secondary storage site with each storage site having read / write access while maintaining zero recovery point objective (RPO) and Zero recovery time objective (RTO), initiating a non-disruptive planned failover (PFO) to change a role for the secondary storage site and change a role for the primary storage site, initiating, with the primary storage site and / or secondary storage site, a PFO out of synchronization (OOS) event that is sent to a mediator agent with no indication of a role for serving IO, and starting a configuration independent unplanned failover if a disaster or site failure occurs during the PFO.

Techniques can include: establishing an asynchronous replication configuration for a replication session of a source volume group VG1 and a target volume group VG2; and performing processing to transition the replication session to a low RPO (recovery point objective) replication mode comprising: setting the replication session to an alternative asynchronous replication (AAR) mode; transitioning the replication session to a hybrid mode; creating a first snapset of snapshots of source volumes of VG1; replicating each snapshot of the first snapset from a source to a target system in either the low RPO replication mode or the AAR mode based on an associated member level asynchronous replication mode corresponding to said each snapshot; and constructing a second snapset of snapshots of target volumes of VG2, wherein each snapshot in the second snapset denotes a same point in time copy as a corresponding snapshot in the first snapset.

A disclosed framework enables virtually any aggressive Recovery Point Objective (RPO) to be enforced for a production database, without limitation on type of database management system (DBMS) or size of the production database. The framework overcomes technological barriers of the prior art, such as bottlenecks presented by a storage manager computer that traditionally managed database backups. To avoid the bottlenecks, an illustrative data storage management system does not engage the storage manager computer in storage operations that could impact the database RPO. Certain components are added and enhanced to autonomously capture database transaction logs, which are stored securely and persistently away from the DBMS. In a separate and less frequent operation, and with involvement of the storage manager computer, the illustrative system generates secondary copies in their final form. Meanwhile, temporary backup files can be used in restore operations without first being converted into secondary copies.

Techniques for adjusting a recovery point objective involve determining a total replication bandwidth and a replication link bandwidth. The total replication bandwidth indicates the sum of replication bandwidths of a plurality of replication sessions, and the replication link bandwidth indicates a maximum bandwidth of a replication link. Such techniques further involve increasing a recovery point objective of the replication link in response to the total replication bandwidth being greater than the replication link bandwidth. The recovery point objective indicates a maximum data loss time range. Such techniques further involve reducing the recovery point objective of the replication link in response to the total replication bandwidth being less than the replication link bandwidth.

This invention discloses a fine-grained disaster recovery method, apparatus, and storage medium for analytical distributed databases. The method includes: globally uniquely mapping the data storage units of each storage node in the primary cluster to the storage locations in the backup cluster based on a pre-established storage layer mapping relationship between the primary and backup clusters; adjusting the synchronization frequency of the primary cluster according to the data change rate, periodically generating synchronization identifiers to identify the global data commit progress, and sending these identifiers to the backup cluster to segment the incremental data synchronization range; and the backup cluster pulling incremental data storage units belonging to the current synchronization range from the primary cluster based on the synchronization identifiers and data synchronization progress. Through block-level incremental identification and direct recovery, adaptive synchronization frequency adjustment, and storage layer mapping between heterogeneous clusters, the method reduces the target recovery point RPO while minimizing the performance impact on the primary cluster and effectively improving the resource utilization of the backup cluster.

To provide a storage system and a data transfer method for suppressing the deterioration of copy performance, and for maintaining short RPO (RecoveryPointObjective).SOLUTION: In a primary storage system, a controller acquires processor load information of the controller and a copy destination storage system, and selects one of a plurality of transfer methods on the basis of a processor load. The plurality of transfer methods include a first transfer method of executing compression processing on the transfer data and a second transfer method of omitting the compression processing on the transfer data or executing the compression processing on the transfer data with a lower processor load than the first transfer method. The selection condition of the first transfer method includes that each processor load of the processor loads of the controller and the copy destination storage system is equal to or less than a threshold value. The selection condition of the second transfer method includes that at least one of processor loads of the controller and the copy destination storage system is higher than a threshold value.SELECTED DRAWING: Figure 11

An embodiment provisions a Validation Area within a consistency group of a primary site and a Validation Area within a consistency group of a secondary site. The embodiment provisions a Validation Writer in the primary site and provisions a Validation Reader in the secondary site; the Validation Writer writes a validation metric into the Validation Area in the primary site at an interval determined by a recovery point objective. The embodiment also reads the validation metric by the Validation Reader in the secondary site, computes a validation result based on the validation metric, the recovery point objective and a recovery point time delta where the validation result comprises an outcome of a replication of the primary site to the secondary site where the Validation Area of the primary site, the Validation Area of the secondary site, the Validation Writer and the Validation Reader are storage and application agnostic.

Systems and methods are provided for bringing a volume of a consistency group (CG) into an in-synchronization (InSync) state while other volumes of the CG remain in the InSync state. According to an example, in order to support recovery from disruptive events in a manner that ensures a zero recovery point objective (RPO) guarantee and insulates an application making use of the CG from adverse impacts, responsive to a triggering event, a Fast Resync process may first be attempted to promptly bring an affected volume back into an in-synchronization (InSync) state from an out of synchronization (OOS) state while allowing other members of the CG to remain in the InSync state. Should the Fast resync process be unsuccessful in bringing the volume back into the InSync state within a predetermined or configurable time threshold, then a second type of resynchronization process may be employed at the CG level.

The invention provides a dynamic data-backup scheduling system. The system includes a memory storing one or more processor-executable routines and a processor communicatively coupled to the memory. The processor is configured to execute one or more processor-executable routines to determine a dynamic backup schedule for one or more computing machines based upon data change patterns of the respective computing machines. The processor is further configured to access user inputs corresponding to data backup for the one or more computing machines. The user inputs comprise at least one of a tolerable data loss threshold, critical data type, file sensitivity data, and exceptions data time period information. The processor is further configured to create one or more service level agreement (SLA) configurations for data backup based on the user inputs. The processor is further configured to access historical data corresponding to one or more data backup cycles of the one or more computing machines. The historical data comprises one or more of time series changes, the addition and / or change of data information for pre-determined data sets, and corresponding file metadata of the data sets. The processor is further configured to implement one of the active and passive modes of data backup using the user inputs and the historical data. The processor is further configured to trigger a backup job for one or more computing machines based on a comparison between the SLA configurations and dynamic information received about data addition and / or data change of the computing machines in the active mode. The processor is further configured to trigger a backup job for one or more computing machines based on a comparison between the SLA configurations and historical time series change and / or addition of data of the computing machines in the passive mode.

An apparatus includes a processing device configured to identify a set of asynchronous data replication sessions currently running on a storage system, each asynchronous data replication session associated with a corresponding recovery point target, and in response to determining that a current synchronization time of at least one of the asynchronous data replication sessions exceeds its corresponding recovery point target for a first iteration of a given time window, compute a session weight for each of the asynchronous data replication sessions. The processing device is further configured to select data from the asynchronous data replication sessions for transmission based at least in part on the computed session weights for a second iteration of the given time window. The processing device is further configured to transmit the selected data during the second iteration of the given time window.

A technique provides network efficient data failover by explicitly protecting one or more common snapshot references at sites of a multi-site data replication environment to improve granularity of control of recovery point objectives (RPO) for data across the sites. A common snapshot reference or recovery point (RP) ensures that, in the event of failure to a site, data designated for failover may be quickly protected by replicating only small incremental changes to the RP so as to maintain RPO requirements across the sites. Illustratively, the technique enhances and extends a disaster recovery (DR) application programming interface (API) protocol through an extension that defines and applies a tag to the RP, wherein the tag enables protection and / or preservation of the RP by ensuring that the sites honor the tag applied to the RP. The tag essentially functions as an advisory lock for the RP that is shared among the sites to prevent deletion of the RP at the sites throughout the duration of the lock.