36 results about "Recovery point objective" patented technology

In one embodiment, a computer-implemented method comprises establishing bi-directional synchronous replication between one or more storage objects of a primary storage site and one or more storage objects 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 resynchronization process due to a loss of the bi-directional synchronous replication between the one or more storage objects and the one or more storage objects, and performing the resynchronization process based on using inflight tracking replay and reconciliation between a first Op log metafile of the primary storage site and a second Op log metafile of the secondary storage site.

In some embodiments, a method for tuning a disaster recovery preparation system for a storage system includes determining whether the disaster recovery preparation system has not met a recovery point objective; and in response to determining that the recovery point objective is not met: determining a state of the storage system; applying a machine learning model to determine a change to one or more of a plurality of adjustable parameters of the disaster recovery preparation system based on the state of the storage system and the recovery point objective that is not met; adjusting the one or more of the plurality of adjustable parameters based on the determined change to the one or more parameters; after adjusting the one or more parameters, monitoring one or more metrics of the disaster recovery preparation system or the storage system; and updating the machine learning model based on the monitoring.

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.

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.

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 for tracking incoming writes and snap creation / deletion in memory to improve asynchronous replication and support lower RPOs. In the techniques, a storage system uses its data cache to receive data specified in write requests issued by storage clients, while dedicating an amount of the cache memory to track and record offsets / lengths of writes directed to source volumes. At the end of each replication interval, the storage system obtains a list of the recorded offsets / lengths for each source volume, identifies and reads areas of the source volume that were written to during the replication interval using the list, and replicates data from the identified areas to a destination volume. Because the list of recorded offsets / lengths of incoming writes for the source volume is compiled and available from volatile cache memory, it can be generated and accessed very quickly using reduced processing / memory resources, allowing for lower RPOs in asynchronous replication processes.

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.

Techniques for tracking incoming writes and snap creation / deletion in memory to improve asynchronous replication and support lower RPOs. In the techniques, a storage system uses its data cache to receive data specified in write requests issued by storage clients, while dedicating an amount of the cache memory to track and record offsets / lengths of writes directed to source volumes. At the end of each replication interval, the storage system obtains a list of the recorded offsets / lengths for each source volume, identifies and reads areas of the source volume that were written to during the replication interval using the list, and replicates data from the identified areas to a destination volume. Because the list of recorded offsets / lengths of incoming writes for the source volume is compiled and available from volatile cache memory, it can be generated and accessed very quickly using reduced processing / memory resources, allowing for lower RPOs in asynchronous replication processes.

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).

The present invention provides a dual-availability zone disaster recovery method, apparatus, electronic device, and storage medium, relating to the field of database technology. The method includes: upon determining that the dual-availability zone connection is normal, a leader node elected from all nodes in the dual-availability zone receives a request and synchronizes logs generated in response to the request to the dual-availability zone. Compared to existing technologies, the present invention provides disaster recovery capabilities with a recovery point objective of zero.

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.

Apparatuses and methods for assessing the recovery viability of backup databases are provided. Some embodiments may include identifying a selected backup database set from the plurality of backup databases. In some embodiments, each backup database in the selected backup database set is associated with a database in a corresponding database set. Some embodiments may include triggering a first backup configuration check operation for each database in the corresponding database set. Some embodiments may include triggering a restore verification operation for each database in the selected backup database set. Some embodiments may include generating a recovery point objective score for each database in the selected backup database set. Some embodiments may include causing updating of a recovery point objective score interface based on the recovery point objective score for each database in the selected backup database set.

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.

Techniques for synchronizing data involve determining, in response to that a replication session in a source cluster is initiated, a recovery point objective (RPO) of the replication session and a plurality of parameters of each device in a plurality of devices in a remote cluster. The plurality of parameters include at least performance headroom and a recovery point objective of a resident replication session. Such techniques further involve selecting a target device from the plurality of devices based on the recovery point objective of the replication session and the plurality of parameters. Such techniques further involve synchronizing data associated with the replication session from the source cluster to the target device in the remote cluster. Accordingly, replication sessions can be evenly distributed across devices, thereby improving resource utilization and data synchronization efficiency, preventing depletion of device utilization, reducing RPO bias, and strengthening the protection for disaster recovery data.

An apparatus comprises a processing device configured to determine syncing progress metrics for replication sessions established between a source and a destination storage system, each of the replication sessions being associated with a recovery point objective and having an assigned bandwidth quota. The processing device is also configured to identify whether a first replication session is not expected to meet its associated first recovery point objective based at least in part on its determined first syncing progress metric and whether at least a second replication session is expected to meet its associated second recovery point objective based at least in part on its determined second syncing progress metric. The processing device is further configured, responsive to identifying the first and second replication sessions, to update a first assigned bandwidth quota for the first replication session and a second assigned bandwidth quota for the second replication session.

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.

A system managing apparatus decides a time optimum for executing data copying from a copy source volume to a copy destination volume, and manages an RPO requirement of a user and a quiescing time period for each application at the time of a copy start. The system managing apparatus calculates a copy execution time and a copy execution interval such that data in which application consistency is maintained can be acquired at an interval that satisfies the RPO. In addition, the system managing apparatus monitors the use status of an application and the use status of a copy line after the start of copy operation, and calculates a copy execution time and a copy execution interval that allow a return to an appropriate recovery point, taking into consideration an application quiescing time period and a period of time required for copy completion that change in real time.

The invention relates to a method, a device and a computer program product for synchronizing data. The method includes, in response to a replication session in a source cluster being initiated, determining a recovery point target (RPO) for the replication session and a plurality of parameters for each of a plurality of devices of a remote cluster, where the plurality of parameters includes at least a performance margin and a recovery point target that resides in the replication session. The method further includes selecting a target device from the plurality of devices based on the recovery point target of the copy session and the plurality of parameters. The method also includes synchronizing data associated with the replication session from the source cluster to a target device in the remote cluster. In this way, copying sessions can be evenly distributed on multiple devices, the device resource utilization rate and the data synchronization efficiency are improved, depletion of the device utilization rate is prevented, RPO deviation is reduced, and therefore protection of disaster recovery data is enhanced.

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.

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.

The present invention provides a method, device and equipment for verifying the recovery point objective of a dual-active disaster recovery system, which are used to solve the technical problems of the efficiency and generality of verifying the recovery point objective (RPO) of a dual-active disaster recovery system. In the present invention, business data is simulated and recorded into a storage system through a script on a selected virtual machine (VM), the reachability of the selected VM is continuously detected at an arbitration node, then a host or site failure is simulated to enable the system to perform a failover of the selected VM, and finally, by analyzing and comparing the timestamp of the last piece of data written by the selected VM before the failure migration and the timestamp of the last reachability detection result of the selected VM recorded by the arbitration node before the migration, it is verified whether the RPO of the dual-active disaster recovery system meets the requirements. The technical solution of the present invention does not need to focus on the underlying storage technology, can cover the scenario where a failure suddenly occurs during the process of the virtual machine writing business data, is simple and easy to use, and has a certain generality.

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.

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).

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.

The invention discloses a data protection method and device, equipment and a storage medium, and the method comprises the steps: simulating a communication protocol of a production database to construct a slave node, and building an authentication connection between the slave node and a master node on the production database; the method comprises the following steps: acquiring a Binlog stream of a production database in real time, and analyzing the Binlog stream to obtain a Binlog event corresponding to the Binlog stream; analyzing and processing the Binlog event to obtain archived data corresponding to the Binlog time; and responding to a received data recovery instruction, and reading a corresponding event from the archived data to carry out data recovery processing. Continuous data capture is achieved through protocol-level log subscription, the limitation of a backup window is eliminated, rapid retrieval is achieved through a marking and archiving mechanism, the recovery accuracy is improved in combination with a reverse SQL generation technology, real-time capture and archiving of database changes are achieved, the recovery point target is effectively reduced to the second level, and the data recovery efficiency is improved.