US10691552B2 - Data protection and recovery system - Google Patents
Data protection and recovery system Download PDFInfo
- Publication number
- US10691552B2 US10691552B2 US14/880,317 US201514880317A US10691552B2 US 10691552 B2 US10691552 B2 US 10691552B2 US 201514880317 A US201514880317 A US 201514880317A US 10691552 B2 US10691552 B2 US 10691552B2
- Authority
- US
- United States
- Prior art keywords
- transfer
- file
- location
- operational information
- time
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
- 238000011084 recovery Methods 0.000 title claims abstract description 77
- 238000012546 transfer Methods 0.000 claims abstract description 60
- 238000000034 method Methods 0.000 claims abstract description 29
- 238000004590 computer program Methods 0.000 claims abstract description 15
- 238000003860 storage Methods 0.000 claims description 38
- 230000015654 memory Effects 0.000 claims description 25
- 230000008569 process Effects 0.000 claims description 10
- 230000009897 systematic effect Effects 0.000 claims description 9
- 230000006872 improvement Effects 0.000 claims description 4
- 238000012417 linear regression Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 16
- 238000004891 communication Methods 0.000 description 15
- 230000006870 function Effects 0.000 description 12
- 230000002085 persistent effect Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 239000004744 fabric Substances 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 230000002441 reversible effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 210000003813 thumb Anatomy 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 238000006424 Flood reaction Methods 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012854 evaluation process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000003442 weekly effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
Definitions
- the present invention relates to data protection and recovery, and more particularly to the estimating of time to recover following a disruptive event.
- DR Disaster recovery
- IT systems have become increasingly critical to the smooth operation of a company, the importance of ensuring the continued operation of those systems, and their rapid recovery, has increased. For example, of companies that had a major loss of business data, 43% never reopen and 29% close within two years. As a result, preparation for continuation or recovery of systems needs to be taken very seriously. This involves a significant investment of time and money with the aim of ensuring minimal losses in the event of a disruptive event.
- Backup-Recovery and DR are critical aspects of a data center management operations. Typically, a significant amount of monitoring and tracking are done to achieve a higher level of service quality to ensure data is protected and it is restorable in case of a disaster.
- An embodiment of the invention may include a method, computer program product and computer system for data recovery.
- the embodiment may include a computing device that determines an amount of time to transfer a first file from a first location to a second location. The first location is on a first device and a second location is on a second device.
- the embodiment may include receiving historical operational information associated with the first device and historical operational information associated with the second device.
- the operational information comprises one or more of: CPU usage, memory usage, and processes running.
- the embodiment may create a transfer model correlating the amount of time to transfer the first file from the first location to the second location with the historical operational information associated with the first device and the historical operational information associated with the second device.
- the embodiment may determine an estimated amount of time to transfer a second file based on the transfer model and a current operational information about the first device and a current operational information about the second device. The embodiment may determine whether the estimated amount of time to transfer a second file is above a first threshold amount.
- FIG. 1 illustrates a data protection and recovery system, in accordance with an embodiment of the invention
- FIG. 2 is a flowchart illustrating the operations of the recovery estimation program of FIG. 1 in determining what document to display based on a shortcut input, in accordance with an embodiment of the invention
- FIG. 3 is a block diagram depicting the hardware components of the computing device and backup device of FIG. 1 , in accordance with an embodiment of the invention.
- RTO Recovery Time Objective
- FIG. 1 illustrates data protection and recovery system 100 , in accordance with an embodiment of the invention.
- data protection and recovery system 100 includes a computing device 110 and a backup device 120 interconnected via a network 130 .
- network 130 is the Internet, representing a worldwide collection of networks and gateways to support communications between devices connected to the Internet.
- Network 130 may include, for example, wired, wireless or fiber optic connections.
- network 130 may be implemented as an intranet, a local area network (LAN), or a wide area network (WAN).
- LAN local area network
- WAN wide area network
- network 130 can be any combination of connections and protocols that will support communications between the computing device 110 and the backup device 120 .
- Backup device 120 may include a backup file 122 .
- Backup device 120 may be a desktop computer, a notebook, a laptop computer, a tablet computer, a handheld device, a smart-phone, a thin client, or any other electronic device or computing system capable of receiving and sending data to and from other computing devices such as computing device 110 via network 130 .
- backup device 120 may be a cluster of web servers executing the same software to collectively process the requests for the web pages as distributed by a front end server and a load balancer.
- backup device 120 is a computing device that is optimized for the support of uploading and downloading data files which reside on backup device 120 , such as backup file 122 , and for the support of network requests related to such files which reside on backup device 120 .
- Backup device 120 is described in more detail with reference to FIG. 3 .
- Backup file 122 includes a collection of data representing a historical snapshot of real time file 114 (explained further below), either from a single point in time (e.g. a full backup of real time file 114 ) or an aggregate of multiple instances in time (e.g. many partial backups of real time file 114 ).
- Backup file 122 may be stored on backup device 120 , but only requires a device with sufficient memory and hard drive space to enable the storage of information on the database.
- Backup file 122 may be used in order to recover information lost from a real time file 114 during a disruptive event.
- Computing device 110 includes recovery estimation program 112 , backup requirements 118 and user interface 126 .
- computing device 110 is a server, a desktop computer, a notebook or a laptop computer; however, in other embodiments, computing device 110 may be a smart phone, a tablet computer, a handheld device, a thin client, or any other electronic device or computing system capable of receiving and sending data to and from backup device 120 via network 130 , and capable of operating a graphical user interface.
- computing device 110 may be a cluster of web servers executing the same software to collectively process the requests for the web pages as distributed by a front end server and a load balancer.
- backup device 120 is a computing device that is optimized for running real time IT systems containing multiple data files, such as real time file 114 . Computing device 110 is described in more detail with reference to FIG. 3 .
- Real time file 114 may be a data file that is being continuously updated as part of an IT regime.
- the data coming in may be any type of real world data, such as web data, consumer data, etc.
- Real time file 114 may be representative of one of many files located on computing device 110 , and may contain metadata pertaining to any distinguishing characteristics of the file, such as the owner of the file, the file's client, etc.
- Real time file 114 may be a file stored using a collection of servers or computer devices, such as computing device 110 .
- Backup requirements 118 may contain information about the RTO requirements pertaining to the real time file 114 , or a group of real time files 114 . Specifically, backup requirements 118 details the acceptable length of time for a backup file 122 to be transferred to the computing device 110 following a disruptive event, so that backup file 122 can replace real time file 114 , to minimize the impact of the disruptive event. Backup requirements 118 may be the downtime that is acceptable during operational failures (e.g. RTO requirement), or may be the acceptable rate of failure to back up a collection of files (e.g. RTO reliability). Backup requirements 118 may be stored on computing device 110 .
- RTO requirement operational failures
- Backup requirements 118 may be stored on computing device 110 .
- Historical backup/recovery information 116 may contain information pertaining to the time needed to accomplish previous transfers of data from real time file 114 to backup file 122 , or conversely. Historical backup/recovery information 116 may relate the time needed to transfer data due to system parameters (e.g. operational information) from previous transfers of data, such as, for example, network speed, size of backup, device load of computing device 110 and backup device 120 , or any other relevant parameters. Historical backup/recovery information 116 may be stored on computing device 110 .
- system parameters e.g. operational information
- Recovery estimation program 112 is a software application or configuration in a software application capable of estimating the time necessary to reestablish a backup file 122 as a real time file 114 following a disruptive event. Recovery estimation program 112 may accomplish this by using the data contained in historical backup/recovery information 116 to create a model. Recovery estimation program 112 may than input operational data detailing the parameters of computing device 110 , backup device 120 and network 130 , into the created model to estimate recovery time during the current system usage. The operations and functions of recovery estimation program 112 are described in further detail below with regard to FIG. 2 .
- FIG. 2 is a flow chart illustrating the steps of the estimation recovery program 112 , in accordance with an embodiment of the invention.
- recovery estimation program 112 creates a backup estimation model using the historical backup/recovery information 116 .
- the backup or recovery jobs may be characterized by job size (1), network speed (2), device load (3) of computing device 110 and backup device 120 (e.g. concurrent back jobs on the same device), and completion time (4).
- Device load may refer to parameters characterizing the performance of a device such as, for example, CPU usage, free memory, processes running, I/O component performance, service status, configuration data, or any other relevant parameters, or how much each of the above parameters are used for the backup or recovery of the current job.
- a model may use information from backup jobs, recovery jobs, or both to create the models.
- the model may take into account a granular (or partial) restore that has occurred. Such instances of a granular restore may occur when a portion of the real time file 114 has been lost, and the files need to be restored from the backup file 122 .
- the information may be appropriately weighted based on differences between backup and restore.
- recovery estimation program 112 may determine any systematic differences for an individual device (or type of device) between upload and download of files, and incorporate the systematic difference into the model by weighting the historical data to account for such systematic differences when creating the model. Further, the model may take into account information (such as job size, network speed, device load and completion time) about data recoveries from backup device 120 to devices similar to computing device 110 . The model created by recovery estimation program 112 can estimate the restore recovery time given the size of the file, network connection and current load of the devices computing device 110 and backup device 120 during the backup of real time file 114 , and additionally may use similar types of information from a granular restoration of real time file 114 .
- the recovery estimation program 112 will use the backup specific configurations of real time file 114 , in order to determine the estimated backup recovery size. For example, if the real time file 114 is configured to have daily full backup, then the estimated backup recovery size for the backup would be the size of the previous backup job size. In another example, if the backup is configured to have weekly full backup using daily increments, or a granular backup, (e.g. daily partial backups of 1/7 th the size), the estimated backup recovery size for the backup would the total of the last 7 daily backups, plus the amount of any day-to-day incremental increase.
- a granular backup e.g. daily partial backups of 1/7 th the size
- the recovery estimation program 112 may estimate the approximate recovery time following a hypothetical disruptive event.
- the recovery estimation program 112 determines the load of computing device 110 , backup device 120 and current network 130 based on the current operating conditions, and uses the estimated backup recovery size from S 220 , to apply the model created by the recovery estimation program 112 in step S 210 , to obtain an estimated recovery time for real time file 114 .
- Such evaluation process can be triggered periodically (e.g., every 15 min), or on-demand. Such processes may occur for multiple real time files 114 located on a computing device 110 , or may be performed based on attributes of the real time files 114 (e.g. client, size, owner).
- the recovery estimation program 112 will compile the estimated recovery time for a given backup given the current operating parameters and compare the estimated recovery time to the backup requirement 118 to determine an RTO reliability.
- the RTO reliability may be a statistical analysis detailing how often restoring the backup file 122 as real time file 114 would not conform to the backup requirements 118 for the specified file.
- the RTO reliability may relate to a period of time (e.g. last month, last year), or may be based on operational criterion (e.g. network load).
- step S 230 of recovery estimation program 112 may be run 100 times, and may meet the RTO requirements 90 times during the week, based on the operating conditions at the time the model estimates the recovery time, then the RTO reliability would be 90%.
- step S 240 may compile average, median, and distribution of the estimated recovery time based on the week of estimated recovery time based on operating conditions.
- the recovery estimation program 112 may determine if the RTO reliability for a specific file, or set of files, is adequate. This may be based on requirements of a specific file (e.g. must maintain RTO 98% of the time for a file), or may be based on objectives for multiple, similar, files (e.g. all files from a certain client must meet 95% RTO). If adequate recovery time is determined, recovery estimation program 112 returns to step S 230 to continue estimating backup time based on the load conditions, checking the estimated recovery time against RTOs. If there is not adequate recovery time, recovery estimation program 112 proceeds to step S 260 .
- the recovery estimation program 112 may alert a user about the inability to meet the defined RTOs contained in backup requirements 118 .
- the recovery estimation program 112 may provide statistics of when RTOs are not met. For example, recovery estimation program 112 may alert the user that in 80% of instances of inadequate recovery time, the amount of processor power allocated to recovery was less than 20%. Additionally, the recovery estimation program 112 may provide possible improvement solutions based on system parameters that are more likely to lead to inadequate recovery time. For example, if the recovery estimation program 112 identifies that more than 60% of the instances of inadequate recovery time are due to inadequate performance of the network 130 , a recommendation may be provided detailing the need to improve network performance.
- FIG. 3 depicts a block diagram of components of computing device 110 and backup device 120 , in accordance with an illustrative embodiment of the present invention. It should be appreciated that FIG. 3 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environment may be made.
- Computing device 110 and backup device 120 include communications fabric 302 , which provides communications between computer processor(s) 304 , memory 306 , persistent storage 308 , communications unit 312 , and input/output (I/O) interface(s) 314 .
- Communications fabric 302 can be implemented with any architecture designed for passing data and/or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within a system.
- processors such as microprocessors, communications and network processors, etc.
- Communications fabric 302 can be implemented with one or more buses.
- Memory 306 and persistent storage 308 are computer-readable storage media.
- memory 306 includes random access memory (RAM) 316 and cache memory 318 .
- RAM random access memory
- cache memory 318 In general, memory 306 can include any suitable volatile or non-volatile computer-readable storage media.
- persistent storage 308 includes a magnetic hard disk drive.
- persistent storage 308 can include a solid state hard drive, a semiconductor storage device, read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, or any other computer-readable storage media that is capable of storing program instructions or digital information.
- the media used by persistent storage 308 may also be removable.
- a removable hard drive may be used for persistent storage 308 .
- Other examples include optical and magnetic disks, thumb drives, and smart cards that are inserted into a drive for transfer onto another computer-readable storage medium that is also part of persistent storage 308 .
- Communications unit 312 in these examples, provides for communications with other data processing systems or devices.
- communications unit 312 includes one or more network interface cards.
- Communications unit 312 may provide communications through the use of either or both physical and wireless communications links.
- the recovery estimation program 112 , real time file 114 , historical backup/recovery information 116 and backup requirements 118 in computing device 110 ; and backup file 122 in backup device 120 may be downloaded to persistent storage 308 through communications unit 312 .
- I/O interface(s) 314 allows for input and output of data with other devices that may be connected to computing device 110 and social media backup device 120 .
- I/O interface 314 may provide a connection to external devices 320 such as a keyboard, keypad, a touch screen, and/or some other suitable input device.
- external devices 320 can also include portable computer-readable storage media such as, for example, thumb drives, portable optical or magnetic disks, and memory cards.
- Software and data used to practice embodiments of the present invention e.g., the recovery estimation program 112 , real time file 114 , historical backup/recovery information 116 and backup requirements 118 in computing device 110 ; and backup file 122 in backup device 120 , can be stored on such portable computer-readable storage media and can be loaded onto persistent storage 308 via I/O interface(s) 314 .
- I/O interface(s) 314 can also connect to a display 322 .
- Display 322 provides a mechanism to display data to a user and may be, for example, a computer monitor.
- each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
- the present invention may be a system, a method, and/or a computer program product.
- the computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
- the computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
- the computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
- a non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
- RAM random access memory
- ROM read-only memory
- EPROM or Flash memory erasable programmable read-only memory
- SRAM static random access memory
- CD-ROM compact disc read-only memory
- DVD digital versatile disk
- memory stick a floppy disk
- a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon
- a computer readable storage medium is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
- Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
- the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.
- a network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
- Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages.
- the computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
- the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
- These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
- the computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
- each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the block may occur out of the order noted in the figures.
- two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
- steps of the disclosed method and components of the disclosed systems and environments have been sequentially or serially identified using numbers and letters, such numbering or lettering is not an indication that such steps must be performed in the order recited, and is merely provided to facilitate clear referencing of the method's steps. Furthermore, steps of the method may be performed in parallel to perform their described functionality.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Retry When Errors Occur (AREA)
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/880,317 US10691552B2 (en) | 2015-10-12 | 2015-10-12 | Data protection and recovery system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/880,317 US10691552B2 (en) | 2015-10-12 | 2015-10-12 | Data protection and recovery system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20170102998A1 US20170102998A1 (en) | 2017-04-13 |
US10691552B2 true US10691552B2 (en) | 2020-06-23 |
Family
ID=58498594
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/880,317 Active 2038-07-21 US10691552B2 (en) | 2015-10-12 | 2015-10-12 | Data protection and recovery system |
Country Status (1)
Country | Link |
---|---|
US (1) | US10691552B2 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11176002B2 (en) * | 2018-12-18 | 2021-11-16 | Storage Engine, Inc. | Methods, apparatuses and systems for cloud-based disaster recovery |
US11521082B2 (en) * | 2019-11-19 | 2022-12-06 | Kyndryl, Inc. | Prediction of a data protection activity time for a backup environment |
US20240111617A1 (en) * | 2022-09-30 | 2024-04-04 | Cohesity, Inc. | Distributed journal for high performance continuous data protection |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030059303A1 (en) * | 1999-12-23 | 2003-03-27 | Noussitou Christian P | Device and method for adjusting the power of a power pack driving a helicopter rotor |
US7092867B2 (en) * | 2000-12-18 | 2006-08-15 | Bae Systems Land & Armaments L.P. | Control system architecture for a multi-component armament system |
US20060224254A1 (en) * | 2005-03-29 | 2006-10-05 | Zarpac, Inc. | Industrial process data acquisition and analysis |
US20080282048A1 (en) * | 2006-12-13 | 2008-11-13 | Fujitsu Limited | Controller, control system, and control program |
US20090313626A1 (en) * | 2008-06-17 | 2009-12-17 | International Business Machines Corporation | Estimating Recovery Times for Data Assets |
US20110082832A1 (en) * | 2009-10-05 | 2011-04-07 | Ramkumar Vadali | Parallelized backup and restore process and system |
US7992031B2 (en) | 2009-07-24 | 2011-08-02 | International Business Machines Corporation | Automated disaster recovery planning |
US20120023041A1 (en) * | 2007-08-08 | 2012-01-26 | Yoram Kariv | System and method for predictive network monitoring |
US8121966B2 (en) | 2008-06-05 | 2012-02-21 | International Business Machines Corporation | Method and system for automated integrated server-network-storage disaster recovery planning |
US8260754B2 (en) * | 2010-05-27 | 2012-09-04 | Hitachi, Ltd. | Computer system and restoration method |
US8370280B1 (en) * | 2011-07-14 | 2013-02-05 | Google Inc. | Combining predictive models in predictive analytical modeling |
US20140081919A1 (en) * | 2012-09-20 | 2014-03-20 | Hitachi, Ltd. | Distributed backup system for determining access destination based on multiple performance indexes |
US20140344805A1 (en) | 2013-05-16 | 2014-11-20 | Vmware, Inc. | Managing Availability of Virtual Machines in Cloud Computing Services |
US20150081639A1 (en) * | 2013-09-18 | 2015-03-19 | International Business Machines Corporation | Optimizing the number and type of database backups to achieve a given recovery time objective (rto) |
-
2015
- 2015-10-12 US US14/880,317 patent/US10691552B2/en active Active
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030059303A1 (en) * | 1999-12-23 | 2003-03-27 | Noussitou Christian P | Device and method for adjusting the power of a power pack driving a helicopter rotor |
US7092867B2 (en) * | 2000-12-18 | 2006-08-15 | Bae Systems Land & Armaments L.P. | Control system architecture for a multi-component armament system |
US20060224254A1 (en) * | 2005-03-29 | 2006-10-05 | Zarpac, Inc. | Industrial process data acquisition and analysis |
US20080282048A1 (en) * | 2006-12-13 | 2008-11-13 | Fujitsu Limited | Controller, control system, and control program |
US20120023041A1 (en) * | 2007-08-08 | 2012-01-26 | Yoram Kariv | System and method for predictive network monitoring |
US8121966B2 (en) | 2008-06-05 | 2012-02-21 | International Business Machines Corporation | Method and system for automated integrated server-network-storage disaster recovery planning |
US8055630B2 (en) | 2008-06-17 | 2011-11-08 | International Business Machines Corporation | Estimating recovery times for data assets |
US20090313626A1 (en) * | 2008-06-17 | 2009-12-17 | International Business Machines Corporation | Estimating Recovery Times for Data Assets |
US7992031B2 (en) | 2009-07-24 | 2011-08-02 | International Business Machines Corporation | Automated disaster recovery planning |
US20110082832A1 (en) * | 2009-10-05 | 2011-04-07 | Ramkumar Vadali | Parallelized backup and restore process and system |
US8260754B2 (en) * | 2010-05-27 | 2012-09-04 | Hitachi, Ltd. | Computer system and restoration method |
US8370280B1 (en) * | 2011-07-14 | 2013-02-05 | Google Inc. | Combining predictive models in predictive analytical modeling |
US20140081919A1 (en) * | 2012-09-20 | 2014-03-20 | Hitachi, Ltd. | Distributed backup system for determining access destination based on multiple performance indexes |
US20140344805A1 (en) | 2013-05-16 | 2014-11-20 | Vmware, Inc. | Managing Availability of Virtual Machines in Cloud Computing Services |
US20150081639A1 (en) * | 2013-09-18 | 2015-03-19 | International Business Machines Corporation | Optimizing the number and type of database backups to achieve a given recovery time objective (rto) |
Non-Patent Citations (1)
Title |
---|
Continuity Central, "Business Continuity Statistics: Where Myth Meets Fact," http://www.continuitycentral.com/feature0660.html, printed on Oct. 6, 2015, pp. 1-9. |
Also Published As
Publication number | Publication date |
---|---|
US20170102998A1 (en) | 2017-04-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11593300B2 (en) | Anomaly-based retention policies for snapshot-based data protection systems | |
US20190278671A1 (en) | Point-in-time copy restore | |
US10331524B2 (en) | Optimizing data backup schedules | |
US9519432B1 (en) | Self-adjusting backup operations | |
US20200278901A1 (en) | Self-learning disaster-avoidance and recovery | |
US10909073B2 (en) | Automatic snapshot and journal retention systems with large data flushes using machine learning | |
US20190163370A1 (en) | Data replication based on data-driven recovery objectives | |
US10248512B2 (en) | Intelligent data protection system scheduling of open files | |
US10216429B2 (en) | Performing post-processing operations for log file writes | |
US10901863B2 (en) | Unified data layer backup system | |
US20220075676A1 (en) | Using a machine learning module to perform preemptive identification and reduction of risk of failure in computational systems | |
US20160350189A1 (en) | Increasing disaster resiliency by having a pod backed up to other peer pods in a site or beyond | |
US11086710B2 (en) | Predictive disaster recovery system | |
US20160019108A1 (en) | Determining alert criteria in a network environment | |
US11829609B2 (en) | Data loss recovery in a secondary storage controller from a primary storage controller | |
US10691552B2 (en) | Data protection and recovery system | |
US11675521B2 (en) | Comprehensive data protection backup | |
US9760450B2 (en) | Restoring a clone point-in-time copy | |
US11809859B2 (en) | Coordinated source code commits utilizing risk and error tolerance | |
US10976941B2 (en) | Validation of storage volumes that are in a peer to peer remote copy relationship | |
US20210034495A1 (en) | Dynamically updating device health scores and weighting factors | |
US11307940B2 (en) | Cognitive data backup | |
US11704164B1 (en) | Intelligent and automatic load balancing of workloads on replication appliances based on appliance load scores | |
US20230032812A1 (en) | Auto-split and auto-merge clusters | |
US20220253522A1 (en) | Continues integration and continues deployment pipeline security |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAVISHI, PANKAJ S.;RAUT, SMITA J.;ROUTRAY, RAMANI R.;AND OTHERS;SIGNING DATES FROM 20150917 TO 20151012;REEL/FRAME:036839/0451 Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, CALIF Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAVISHI, PANKAJ S.;RAUT, SMITA J.;ROUTRAY, RAMANI R.;AND OTHERS;SIGNING DATES FROM 20150917 TO 20151012;REEL/FRAME:036839/0451 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |