31 results about "Recovery point objective" patented technology

A distribution plan that indicates how to encode and distribute backup data across multiple data centers may be generated. The distribution plan may be generated such that one or more characteristics of the distribution plan, such as costs, are optimized while constraints on the plan, such as protection level, recovery point objective (RPO), and recovery time objective (RTO) are satisfied. The protection level may indicate the number of the data centers that are to remain available such that the backup data is recoverable from encoded fragments of the backup data stored in the data centers that remain available.

A system is provided for storage of journal data from a primary site to a secondary site with a predefined quality of service. In one implementation, the primary storage system stores information for updating data stored on the primary disk array in the form of a history of updates made to the data. The primary storage system is configured to transfer this journal information to the secondary storage system. The user can specify the quality of service desired using a variety of measures, for example, a recovery point objective or a recovery time objective. In response, a copy manager within one of the storage systems determines the capacity of the various primary and secondary volumes, and determines the copy rate available, typically dependent upon the bandwidth between the primary and secondary systems. The copy manager then copies journal data to the remote site where it is stored.

A system for disaster recovery including a controller (i) for controlling bandwidth usage of a disaster recovery system in accordance with a plurality of recovery point objectives (RPOs), each RPO designating a maximal time loss constraint for data recovery for an enterprise production system, and a corresponding bandwidth allocation for the disaster recovery system to use in replicating data for the enterprise production system, wherein the RPOs are applied in accordance with a calendar-based schedule of dates and times, and (ii) for issuing an RPO alert when the RPO maximal time loss constraint for a current date and time is not satisfied.

A mirrored storage system for applications is provided, which enables and supports the variation and dynamic adaptation of the Recovery Point Objectives (RPO) based on policies. Furthermore, methods are provided for running such a mirrored storage system. Said mirrored storage system comprises a first storage system and at least one further storage system, wherein said first and said further storage system are connected via at least one mirror link. An application accesses said mirrored storage system via a network. Therewith, the data to be stored as response to a write command of said application can be mirrored according to a configurable time-varying RPO requirement of the application transmitting the corresponding write command.

A method, executed by a computer, for allocating resources includes assigning resiliency attributes to a server having a workload, linking each server to a partner resource, duplicating the workload of each server in an offsite location accessible to the partner resource, detecting a disaster event, and transferring the workload of the server automatically to the partner resource. In some embodiments, the partner resource is a plurality of pool servers. The partner resource may be calculated by performing a capacity analysis. The partner resource may not a specifically assigned resource until a disaster occurs. In some embodiments, the workload is duplicated such that the recovery point objective of the workload is minimized. A computer program product and computer system corresponding to the methods are also disclosed herein.

Example implementations described herein are directed to automated failover and assuring RTO (Recovery Time Objective) assurance, and RPO (Recovery Point Objective) on asynchronous remote copy feature of storage. By using markers that are cyclically stored to the journal volume, the storage device can thereby determine an accurate communication loss period.

An improved data replication system with goals of Recovery Point Objective of zero, meaning a zero potential for loss of data, and a Recovery Time Objective in the seconds, meaning very short downtime after a failure. The system includes duplicates of a data set preferably on multiple drives in multiple computers. Change requests are stored within duplicates, and when a change request has been stored in enough duplicates, it may be applied to any duplicate after all prior change requests have been applied to that duplicate. The system applies changes to duplicates of a data set in the same order. The system further includes a replicator operable to implement accessing and changing steps to meet the goals.

Embodiments for an approach to resource optimization during consistency group formation associated with a global mirror environment is provided. The approach detects when a primary volume associated with the consistency group has completed transmitting its out-of-sync (OOS) data towards its associated secondary volume. A command is sent to create a next consistency group sidefile so further writes can be sent to the sidefile rather than queueing at the primary volume. The approach repeats this process for each primary volume associated with the global mirror environment until all primary volumes are complete. Commands are sent to disable writes to the associated sidefiles and to merge the data stored in the sidefiles into normal cache as the next consistency group becomes the current consistency group.

The invention provides a method for calculating a disaster recovery point objective of an information system. The key of the method is an information system consisting of m production systems, wherein k items of services K1, K2,..., Kk run on the information system, and each item of service only can run on one production system. Through analyzing the importance of each production system, the importance of each service, the existing data volume and the data volume (per second) generated by each department in the information system, and based on the generated data volume (per second) relevant to each service, according to the percentage of the existing data volume in a service used by a department to the total data volume of the department, new generated data (per second) of each service and new generated data (per second) of the production system relevant to each service are estimated; and then, through synthesizing the importance of each production system in the information system, the generated data volume of a production system is divided by the newly increased weighted data volume of the production system so as to obtain a value of the disaster RPO (recovery point objective) of the whole information system.