WO2009026028A2 - Staged, lightweight backup system - Google Patents
Staged, lightweight backup system Download PDFInfo
- Publication number
- WO2009026028A2 WO2009026028A2 PCT/US2008/072822 US2008072822W WO2009026028A2 WO 2009026028 A2 WO2009026028 A2 WO 2009026028A2 US 2008072822 W US2008072822 W US 2008072822W WO 2009026028 A2 WO2009026028 A2 WO 2009026028A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- functions
- backup
- data
- state
- system state
- Prior art date
Links
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
-
- 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/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1441—Resetting or repowering
-
- 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/1466—Management of the backup or restore process to make the backup process non-disruptive
Definitions
- Backup and restore systems are commonly deployed on many computer systems and other devices that contain data. Such backup and restore systems may copy data from one source, such as a hard disk or other data storage system, to another source, such as an offsite data repository, removable tape or optical storage system, or other device.
- a new set of data storage media may be created or the original media overwritten to create a data source that is capable of operating as the original media.
- a hardware failure may cause the replacement of data storage hardware, which may have the data recreated from a backup data location.
- a corruption, misconfiguration, or other damage to stored data may be cause for data to be overwritten with a known good version of data from a previous backup.
- backup and restore operations may be very time consuming.
- a working copy of a data set may be used to create a backup while other operations continue.
- Such a system may consume some processor bandwidth, but may keep the system in an operable state.
- a large amount of data may be transferred consuming a large amount of time, during which a system may not be operable until the restore operation is complete.
- a restore system may perform a two staged restore operation.
- the first operation may restore system state and basic operational data to a system sufficient that the system may begin performing a set of basic operations.
- the second operation may restore secondary data over a period of time while the system is at least partially operational.
- the system state and basic operational data may be identified and backed up in a separate operation than the secondary data, or may be extracted from a backup volume of the system.
- the system state restore may be performed by installing a base set of data or applications and applying specific system state information.
- FIGURE 1 is a diagram illustration of an embodiment showing a system that may be used for staged restore.
- FIGURE 2 is a flowchart illustration of an embodiment showing a backup operation.
- FIGURE 3 is a flowchart illustration of an embodiment showing a staged restore operation with predetermined functions.
- FIGURE 4 is a flowchart illustration of an embodiment showing a staged restore operation without predetermined functions.
- a backup and restore system may use a system state to quickly configure and start certain functions before restoring other data.
- the system may allow certain functions, such as server related network functions or other identified functions, to be up and running quickly, even when a full system restore may take many minutes or even hours.
- the system state may be a small subset of state variables that may be injected into a basic configuration of a system to cause the system to begin to perform certain functions. While the functions are performing, the remaining backup data may be restored.
- Other embodiments may use different techniques for saving and using system state definitions.
- the system may be used to recover from a hardware failure, such as the failure of a disk drive or other storage device.
- the system may be used to migrate a system from an older hardware platform to a new hardware platform.
- the system may be used to revert to a previously saved or backed up configuration.
- the subject matter may be embodied as devices, systems, methods, and/or computer program products. Accordingly, some or all of the subject matter may be embodied in hardware and/or in software (including firmware, resident software, micro-code, state machines, gate arrays, etc.) Furthermore, the subject matter may take the form of a computer program product on a computer-usable or computer- readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system.
- a computer-usable or computer- readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
- the computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium.
- computer readable media may comprise computer storage media and communication media.
- Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by an instruction execution system.
- the computer-usable or computer-readable medium could be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, of otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
- Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media.
- FIG. 1 is a diagram of an embodiment 100 showing a system that may be backed up and restored in two stages. In a first stage, various system functions may be installed and configured to operate, then the remaining data may be restored while the system functions are operating.
- the diagram of Figure 1 illustrates functional components of a system.
- the component may be a hardware component, a software component, or a combination of hardware and software.
- Some of the components may be application level software, while other components may be operating system level components.
- the connection of one component to another may be a close connection where two or more components are operating on a single hardware platform. In other cases, the connections may be made over network connections spanning long distances.
- Each embodiment may use different hardware, software, and interconnection architectures to achieve the functions described.
- the system 102 may be a computer, such as a server computer, that may perform certain services or functions. When the system 102 is restored from a backup, some functions may be started operating before other data are restored.
- the system 102 may be any type of device with a data storage system 104 that may have some system functions 106 that are to be restored prior to other data on the data storage system 104. Examples of such devices may be personal computers, server computers, personal digital assistants, network appliances, game consoles, entertainment systems, wireless communication devices, industrial controllers, network routers, or any other device that contains a data storage system.
- Data backup and restore systems are used in many situations where the system 102 or data in its data storage system 104 have high value functions.
- the server may perform various network management or data management functions across a network for many client devices.
- a server may host various applications that are used by clients across a network, such as an accounting system or email system that may be shared by several users. When such high value systems or data are disrupted, the devices and users that depend on the system or data may be unable to perform their assigned tasks.
- the system 102 may use the data storage system 104 to store various code that is executed by the system 102. Such code may include operating system level code and application level code.
- operating system level code may perform various low level functions, including network connectivity, low level device interfaces, and various services that may be used by the system 102 and other devices attached to a network 112.
- Application level code may operate within an operating system environment and provide many different functions, from accounting systems and email systems to games, web hosting, or any type of function.
- a backup system may store data in any useful format so that the data storage system 104 may be recreated.
- a backup system may attempt to recreate the data storage system 104 on a bit-by-bit level by backing up and recreating an image of the data storage system 104.
- a backup system may make copies of individual files found in the data storage system 104, and individual files may be restored to the data storage system 104 during a restore operation.
- Some backup systems may give a user or administrator the ability to restore portions of a file system. For example, a user may be able to select individual files to restore. Such systems are useful in cases where a user unintentionally or inadvertently deletes or changes a file and wishes to revert back to a previously backed up version.
- the system 102 may be backed up on a regular basis.
- a backup system may be configured to perform a backup operation on a recurring basis, such as every night or on weekends when the system usage may be low.
- the backup system may transfer backup data over a network 112 to a backup data storage 106 that may be located on a different device on a local area network or accessed via the Internet to an offsite device.
- the time to perform a full restore operation may be quite lengthy. In many cases, even with high speed network connections, a standard personal computer may take one or more hours to restore.
- Restore operations are often responses to catastrophic failures of hardware, such as the crashing or corruption of a disk drive, failure of a motherboard, damage due to a voltage spike, or some other failure. In such cases, a failed hardware component may cause an individual component or the entire system to be replaced.
- Restore operations may also be performed after a virus, worm, or other malicious software infiltrates a file system, after an update or installation of an application or operating system is aborted, a user mistakenly or maliciously deletes sensitive data, or for some other situation where a decision is made to revert to a previous version of the data on the data storage system 104.
- a restore operation may be used to migrate an operating system, applications, and functions from one hardware platform to another hardware platform. An example may be when a server computer is upgraded by replacing the entire server hardware with a new server hardware that may include a new data storage system 104.
- the restore operation may be performed in two stages.
- a first stage a set of identified system functions 106 may be installed and configured with system state data 110.
- the system functions 106 may be started operating in the first phase while, in the second phase, remaining data may be restored to the data storage system 104.
- the first stage of installing and configuring the system functions 106 may be performed in a matter of minutes while the second stage of copying large amounts of other data may be performed in a matter of several hours.
- the system functions 106 may be used by other devices and users even though the system restore may not be complete.
- the system 102 may be a server computer and may perform several network related functions, such as Domain Name Sever (DNS) or Dynamic Host Configuration Protocol (DHCP) services. Such functions may be part of an operating system or application function that enables other devices or users to connect to a network. In such an example, if the server 102 were down for several hours performing a restore operation without enabling the DNS or DHCP services, many users may be prevented from performing other tasks.
- DNS Domain Name Sever
- DHCP Dynamic Host Configuration Protocol
- Other examples of such functions include various network functions, email application functions, domain name service functions, dynamic host configuration protocol functions, remote access functions, virtual private network functions, web hosting functions, and firewall functions.
- a set of system state data 110 may be used to configure the system functions 106 during a first stage of the restore operation.
- a standard system image 114 or some other generic set of operating system or application files and data may be installed on the data storage system 104.
- the system state data 110 may be injected or used to configure the various system functions 106 so that the functions operate in the same manner as when the backup operation was performed.
- a system function 106 may include connecting to a network with a specific host name and operating a DNS function.
- a standard system image 114 of a server operating system may be written onto the data storage system 104 and the system state data 110 may be used to configure the system network connection with the same host name and operate the DNS service with the same parameters as when the system 102 was backed up.
- the standard system image 114 may be obtained from an installation disk or other source than the backup data storage system 106.
- the standard system image 114 may be an actual disk image that is used to create a starting image for the restore process while in other cases, the standard system image 114 may be a collection of generic files that may be supplied using a set of installation disks.
- the system state data 110 may be separately stored during a backup operation. In some cases, the system state data 110 may be determined by analyzing the backup data 108.
- FIG. 200 is a flowchart illustration of an embodiment 200 showing a method for a backup operation.
- Embodiment 200 illustrates a backup operation that identifies certain system state functions that are to be configured and operated during a first stage of a backup operation. Each function may be an operating system level function or may be a separate application or other function. For each function, data are identified that may be used during a restore operation to configure and launch the function prior to restoring other data.
- Embodiment 200 creates a backup operation that may be performed many times.
- the backup operation is begun in block 202 and volumes to back up are identified in block 204.
- the volumes may be any logical data storage device.
- a volume may be made up of multiple physical data storage devices, such as a Redundant Array of Independent Disks (RAID) configuration.
- RAID Redundant Array of Independent Disks
- a single device such as a hard disk may contain two or more volumes.
- a volume may be contained within a volatile or non-volatile memory system such as a flash memory or other device capable of storing data.
- Functions for system state restore are identified in block 206.
- the functions identified in block 206 may be any type of function, including operating system functions and application functions.
- the functions for system state restore may be portions of an operating system while in other cases, the functions may be contained in applications that are installed and operated within an operating system environment.
- the state variables for the function are identified in block 212.
- the identified variables of block 212 may be configuration files, registry entries, or other variables or definitions that may be used during a restore operation to configure the function for operation.
- the state variables are identified in block 216.
- the clean configuration of block 214 may include a set of installation files, portion of a disk image, or other set of function definitions that may or may not include the state variables of block 216.
- a clean configuration may include a set of installation disks available on media that may be used during a restore operation.
- all files related to the function may be identified in block 218 and the state variables may be identified in block 220.
- the files relating to the function may be identified for separate backup in block 218. Such files may be used to recreate the function during a restore operation so that the function may operate during a second restore stage.
- data are identified that may be used to recreate and restart the function.
- the operating system may be installed and initially configured to perform a designated function as well as some functions defined by various applications.
- the operating system and applications may be installed from an installation disk or other medium that may be separate from the backup data storage medium.
- the state variables may be used to configure and launch the various functions.
- a backup system may identify the various files that make up the function so that the function may be restored and operational during a first restore stage.
- a backup system may create a separate volume or backup storage area in which to store the state variables and any files relating to the functions to be installed and started in the first stage of restore. In such cases, the separate backup storage area may be able to be copied to a portable disk or other media for use during the restore process.
- the backup storage location may be identified in block 222.
- the backup storage location may be a backup storage device attached to the system to be backed up. An example may be a tape backup system, writeable optical storage system, or backup hard disk system.
- the backup storage location may have removable media so that the media may be stored in a secure location such as a vault or safe deposit box.
- the backup storage location may be a backup storage device that is accessed over a network, include a local area network or the Internet. In some such embodiments, a backup storage device may be used to store backup data from many different systems.
- Some embodiments may use data compression and/or data encryption for the data that are stored in a backup storage system.
- the backup operation may be scheduled in block 224 and run in block 226. In many embodiments, a backup operation may be scheduled to be performed during periods of low usage, such as at night or during weekends.
- Some backup systems may be configured to perform full backups in some instances and incremental backups at other times. Incremental backups may be used to store the data that has changed since the last backup was performed. In some many cases, a full backup may produce a large set of backup data, but the incremental backups may produce only a small fraction of such data and may be performed more rapidly and take up less space than performing a full backup.
- Any backup technology may be employed to perform the actual backup operation.
- FIG. 3 is a flowchart illustration of an embodiment 300 showing a method for restoring using a staged restore operation.
- Embodiment 300 is one method by which a set of pre-defined functions are installed, configured, and started before a bulk of the restore operation may be performed.
- Embodiment 300 is for those cases where functions are defined ahead of time and may have state variables or files separately stored during a previous backup operation.
- Embodiment 400 illustrated later in this specification, illustrates an embodiment where these functions are defined after the backup operation has been performed.
- the device being restored is brought offline in block 304 and enters a pre- installation environment in block 306.
- Some systems may have a pre-installation environment that may enable rapid installation and configuration of operating system functions and applications to the system.
- the pre-installation environment of block 306 may be started by booting a system using a restore disk or an operating system installation disk.
- a system may have a new or clean version of an operating system installed and configured.
- a partition within a hard disk or other data storage area may contain an image of an operable operating system. Such an image may be written onto the system being restored so that the system may at least become partially operational.
- the function For each function with state variable storage in block 308, the function will be installed and configured. If the function is to be installed from backed up files for the function or application in block 310, the function is installed and configured using stored files in block 312. A full copy of the function may be installed if the function is not included in a base version of the operating system or other image used to operate the device during the initial portion of the restore operation. [0062] If the function is not contained in backup files but defined in installation disks, default system image, or some other installation medium in block 310, the generic image is installed in block 314.
- State variables are injected into the installation in block 316.
- the method of injecting state variables may include overwriting configuration files, making registry entries, or other configuration actions.
- the pre-installation environment may be exited in block 318 and the operating system started in block 320.
- Each of the functions may be started in block 322 and the remaining backed up data may be restored in block 324.
- Each embodiment may use different techniques and sequences for loading and configuring functions that may be operational during a second stage of restoring. Some embodiments may or may not use a pre-installation environment as in blocks 306 and 318 for performing the installation and configuration of the various functions.
- Such embodiments may use a first operating system to load and configure a data storage system which may be a bootable data storage system with a second operating system.
- Other embodiments may install and load a single operating system that may be configured to perform the various functions.
- the restoring of remaining data in block 324 may include restoring applications, functions, as well as raw data that may be stored or operate on the device.
- the applications or functions that are restored and configured during block 324 may be those functions that are selected to be operable after a set of higher priority applications or functions that may be started in block 322.
- FIG. 400 is a flowchart illustration of an embodiment 400 showing a method for a staged restore without predetermined state variables.
- Embodiment 400 is a method whereby certain functions may be identified for the first stage of a restore operation, and the state variables for those functions are derived from an analysis of a backup data set. Once the state variables are discovered, the functions are loaded, configured, and started before other remaining data are restored.
- a volume to restore is identified in block 402. In many backup and restore systems, a backup operation may create several volumes of backup data.
- Functions for first stage restore are identified in block 404. In some embodiments, the functions may be selected from a list of possible choices.
- the backup volume may be searched for state variable information in block 408. The state variables for the various functions may be located in many different locations, including configuration files, registry settings, or other locations.
- a pre-installation environment may be entered in block 410.
- a generic image of an operating system may be installed in block 412 and the state variables may be injected in block 414 to configure the various functions.
- the operating system may be started in block 418 and the functions begun in block 420.
- the remaining data may be restored in block 422.
- the operations of block 402 through 408 may be performed using an application on a device other than the device for which a restore operation is planned.
- a first server device is scheduled for the restore operation, and a second server may host the data storage device on which the backup data for the first server is stored.
- An application running on the second server may be used to identify functions for first stage restore and search the backup volume to extract the state variables.
- Such an application may also create an initial install disk or image that may be loaded onto the first server.
- the first server may then be booted using the install disk or image, begin the function operations, and restore the remaining data.
- Each embodiment may use different sequences and various processes for installing, configuring, and executing various functions prior to performing a second stage of restoring.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2008801034559A CN101784995B (en) | 2007-08-23 | 2008-08-11 | Staged, lightweight backup system |
EP08797637A EP2191378A4 (en) | 2007-08-23 | 2008-08-11 | Staged, lightweight backup system |
RU2010106179/08A RU2483349C2 (en) | 2007-08-23 | 2008-08-11 | Staged, lightweight backup system |
BRPI0812960-6A BRPI0812960B1 (en) | 2007-08-23 | 2008-08-11 | METHOD TO PERFORM A GRADUAL RECOVERY AND RESTORATION OF A DATA STORAGE SYSTEM, LEGIBLE MEANS BY COMPUTER AND SYSTEM FOR GRADUAL RECOVERY AND RESTORATION |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/844,351 | 2007-08-23 | ||
US11/844,351 US7788234B2 (en) | 2007-08-23 | 2007-08-23 | Staged, lightweight backup system |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2009026028A2 true WO2009026028A2 (en) | 2009-02-26 |
WO2009026028A3 WO2009026028A3 (en) | 2009-04-16 |
Family
ID=40378914
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2008/072822 WO2009026028A2 (en) | 2007-08-23 | 2008-08-11 | Staged, lightweight backup system |
Country Status (6)
Country | Link |
---|---|
US (1) | US7788234B2 (en) |
EP (1) | EP2191378A4 (en) |
CN (1) | CN101784995B (en) |
BR (1) | BRPI0812960B1 (en) |
RU (1) | RU2483349C2 (en) |
WO (1) | WO2009026028A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2471715A (en) * | 2009-07-10 | 2011-01-12 | Hewlett Packard Development Co | Determining the data chunks to be used as seed data to restore a database, from manifests of chunks stored in a de-duplicated data chunk store. |
EP2454670A2 (en) * | 2009-07-15 | 2012-05-23 | Iron Mountain Incorporated | Operating system restoration using remote backup system and local system restore function |
Families Citing this family (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8204863B2 (en) * | 2009-12-21 | 2012-06-19 | International Business Machines Corporation | Multi-phase file system restore with selective on-demand data availability |
CN102999347B (en) * | 2011-09-15 | 2015-07-29 | 腾讯科技(深圳)有限公司 | A kind of system reloading method, system and client |
US8639665B2 (en) | 2012-04-04 | 2014-01-28 | International Business Machines Corporation | Hybrid backup and restore of very large file system using metadata image backup and traditional backup |
CN102707968A (en) * | 2012-04-12 | 2012-10-03 | 华平信息技术股份有限公司 | Method and system for generating installation backup system |
US9164849B2 (en) * | 2012-04-30 | 2015-10-20 | Hewlett-Packard Development Company, L.P. | Backup jobs scheduling optimization |
US8914334B2 (en) | 2012-09-12 | 2014-12-16 | International Business Machines Corporation | Using a metadata image of a file system and archive instance to restore data objects in the file system |
US8805789B2 (en) | 2012-09-12 | 2014-08-12 | International Business Machines Corporation | Using a metadata image of a file system and archive instance to backup data objects in the file system |
CN103713963B (en) * | 2012-09-29 | 2017-06-23 | 南京壹进制信息技术股份有限公司 | A kind of efficient file backup and restoration methods |
CN103793290B (en) * | 2012-10-31 | 2018-03-09 | 腾讯科技(深圳)有限公司 | A kind of disaster tolerance system and its method for reading data |
CN103838642B (en) * | 2012-11-26 | 2018-03-13 | 腾讯科技(深圳)有限公司 | A kind of data reconstruction method, device and system |
US20140250077A1 (en) * | 2013-03-01 | 2014-09-04 | Storagecraft Technology Corporation | Deduplication vault storage seeding |
JP5949732B2 (en) * | 2013-11-27 | 2016-07-13 | 株式会社オートネットワーク技術研究所 | Program update system and program update method |
US9354979B2 (en) | 2014-02-07 | 2016-05-31 | International Business Machines Corporation | Server based disaster recovery by making use of dual write responses |
CN104615465B (en) * | 2015-01-30 | 2019-04-23 | 深圳市金立通信设备有限公司 | A kind of terminal |
CN105045677A (en) * | 2015-06-30 | 2015-11-11 | 浪潮(北京)电子信息产业有限公司 | Recovery method and device of parameter file |
CN105095020B (en) * | 2015-07-21 | 2018-02-27 | 中国船舶重工集团公司第七0九研究所 | System backup and recovery device and its method suitable for on-chip system |
CN105068894A (en) * | 2015-09-10 | 2015-11-18 | 浪潮(北京)电子信息产业有限公司 | Method and device for achieving high availability of Linux system storage device on basis of LVM mirror image |
US10169174B2 (en) | 2016-02-29 | 2019-01-01 | International Business Machines Corporation | Disaster recovery as a service using virtualization technique |
US11061776B2 (en) | 2017-08-07 | 2021-07-13 | Datto, Inc. | Prioritization and source-nonspecific based virtual machine recovery apparatuses, methods and systems |
US11061713B2 (en) | 2017-08-07 | 2021-07-13 | Datto, Inc. | Prioritization and source-nonspecific based virtual machine recovery apparatuses, methods and systems |
US11036422B2 (en) | 2017-08-07 | 2021-06-15 | Datto, Inc. | Prioritization and source-nonspecific based virtual machine recovery apparatuses, methods and systems |
RU2746187C1 (en) * | 2020-05-06 | 2021-04-08 | Александр Сергеевич Хлебущев | Method for backup of data block versions, machine-readable media and system for using this method |
CN111769903A (en) * | 2020-06-09 | 2020-10-13 | 国家数字交换系统工程技术研究中心 | Network security defense method applied to network security defense system and related device |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1199636A2 (en) | 2000-10-06 | 2002-04-24 | Hewlett-Packard Company | Self-repairing operating system for computer entities |
WO2007017857A1 (en) | 2005-04-15 | 2007-02-15 | Zak Dechovich | Accelerated computer recovery |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5797016A (en) * | 1996-10-29 | 1998-08-18 | Cheyenne Software Inc. | Regeneration agent for back-up software |
US6820214B1 (en) * | 1999-07-26 | 2004-11-16 | Microsoft Corporation | Automated system recovery via backup and restoration of system state |
US6892221B2 (en) | 2000-05-19 | 2005-05-10 | Centerbeam | Data backup |
US7039830B2 (en) | 2000-12-14 | 2006-05-02 | Far Stone Technology Corporation | Backup/recovery system and methods for protecting a computer system |
US6944790B2 (en) * | 2001-04-05 | 2005-09-13 | International Business Machines Corporation | System and method for collecting and restoring user environment data using removable storage |
US7165154B2 (en) | 2002-03-18 | 2007-01-16 | Net Integration Technologies Inc. | System and method for data backup |
US6981177B2 (en) | 2002-04-19 | 2005-12-27 | Computer Associates Think, Inc. | Method and system for disaster recovery |
CN100589064C (en) * | 2002-09-06 | 2010-02-10 | 马克斯托公司 | Method and apparatus for realizing single button external backup |
US7194652B2 (en) * | 2002-10-29 | 2007-03-20 | Brocade Communications Systems, Inc. | High availability synchronization architecture |
US20050039069A1 (en) | 2003-04-03 | 2005-02-17 | Anand Prahlad | Remote disaster data recovery system and method |
JP4267420B2 (en) | 2003-10-20 | 2009-05-27 | 株式会社日立製作所 | Storage apparatus and backup acquisition method |
CN1894936B (en) * | 2003-11-21 | 2010-12-22 | 尼姆凯特网络公司 | Back up of network devices |
US7536424B2 (en) | 2004-05-02 | 2009-05-19 | Yoram Barzilai | System and methods for efficiently managing incremental data backup revisions |
CN1315048C (en) * | 2004-07-06 | 2007-05-09 | 天津百维软件科技有限公司 | A memory-space saving multi-computer system sharing backup method |
US7756833B2 (en) * | 2004-09-22 | 2010-07-13 | Microsoft Corporation | Method and system for synthetic backup and restore |
US8423573B2 (en) * | 2004-11-12 | 2013-04-16 | International Business Machines Corporation | Filesystem backup using directorywise hardlinking for a computer filesystem |
US8335770B2 (en) | 2005-02-03 | 2012-12-18 | Hewlett-Packard Development Company, L.P. | Method of restoring data |
US7483929B2 (en) | 2005-02-08 | 2009-01-27 | Pro Softnet Corporation | Systems and methods for storing, backing up and recovering computer data files |
CN100337211C (en) * | 2005-06-10 | 2007-09-12 | 张健 | Method for safeguarding the continuous safety operation of computers |
US9122643B2 (en) | 2005-12-08 | 2015-09-01 | Nvidia Corporation | Event trigger based data backup services |
US20070168401A1 (en) * | 2006-01-05 | 2007-07-19 | Aditya Kapoor | User interface for piecemeal restore |
US7747575B2 (en) * | 2006-11-07 | 2010-06-29 | Magix Ag | Application-specific intelligent backup and restore system |
-
2007
- 2007-08-23 US US11/844,351 patent/US7788234B2/en active Active
-
2008
- 2008-08-11 EP EP08797637A patent/EP2191378A4/en not_active Ceased
- 2008-08-11 WO PCT/US2008/072822 patent/WO2009026028A2/en active Application Filing
- 2008-08-11 BR BRPI0812960-6A patent/BRPI0812960B1/en active IP Right Grant
- 2008-08-11 CN CN2008801034559A patent/CN101784995B/en active Active
- 2008-08-11 RU RU2010106179/08A patent/RU2483349C2/en active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1199636A2 (en) | 2000-10-06 | 2002-04-24 | Hewlett-Packard Company | Self-repairing operating system for computer entities |
WO2007017857A1 (en) | 2005-04-15 | 2007-02-15 | Zak Dechovich | Accelerated computer recovery |
Non-Patent Citations (1)
Title |
---|
See also references of EP2191378A4 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2471715A (en) * | 2009-07-10 | 2011-01-12 | Hewlett Packard Development Co | Determining the data chunks to be used as seed data to restore a database, from manifests of chunks stored in a de-duplicated data chunk store. |
US8566519B2 (en) | 2009-07-10 | 2013-10-22 | Hewlett-Packard Development Company, L.P. | Providing preferred seed data for seeding a data deduplicating storage system |
EP2454670A2 (en) * | 2009-07-15 | 2012-05-23 | Iron Mountain Incorporated | Operating system restoration using remote backup system and local system restore function |
EP2454670A4 (en) * | 2009-07-15 | 2014-12-31 | Iron Mountain Inc | Operating system restoration using remote backup system and local system restore function |
Also Published As
Publication number | Publication date |
---|---|
RU2483349C2 (en) | 2013-05-27 |
CN101784995B (en) | 2012-06-20 |
EP2191378A4 (en) | 2012-08-01 |
RU2010106179A (en) | 2011-08-27 |
BRPI0812960B1 (en) | 2020-03-31 |
US7788234B2 (en) | 2010-08-31 |
US20090055446A1 (en) | 2009-02-26 |
WO2009026028A3 (en) | 2009-04-16 |
BRPI0812960A2 (en) | 2014-12-09 |
EP2191378A2 (en) | 2010-06-02 |
CN101784995A (en) | 2010-07-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7788234B2 (en) | Staged, lightweight backup system | |
US11675670B2 (en) | Automated disaster recovery system and method | |
RU2495481C2 (en) | Software deployment in large-scale network systems | |
US8302091B2 (en) | Installation of a bootable image for modifying the operational environment of a computing system | |
US7669021B2 (en) | File system based offline disk management | |
US8407189B2 (en) | Finding and fixing stability problems in personal computer systems | |
US20050289533A1 (en) | Method and system for updating a software image | |
US20110173430A1 (en) | IT Automation Appliance Imaging System and Method | |
US7694169B2 (en) | Restoring a client device | |
US10331427B2 (en) | Capturing and deploying an operation system in a computer environment | |
US20020194533A1 (en) | External repair of a computer | |
US9846621B1 (en) | Disaster recovery—multiple restore options and automatic management of restored computing devices | |
US9619340B1 (en) | Disaster recovery on dissimilar hardware | |
KR100831128B1 (en) | System and method for backup/recovery of operating system, backup/recovery/update/install/run of game program and management of operating sysem | |
KR100792786B1 (en) | Method for os restoring of computer using backup image file | |
Galiano Molina | Advanced OS deployment system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200880103455.9 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08797637 Country of ref document: EP Kind code of ref document: A2 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 664/CHENP/2010 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010106179 Country of ref document: RU |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008797637 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: PI0812960 Country of ref document: BR Kind code of ref document: A2 Effective date: 20091228 |