[go: up one dir, main page]

WO2003048935A1 - Systemes et procedes de retablissement d'ordinateurs - Google Patents

Systemes et procedes de retablissement d'ordinateurs Download PDF

Info

Publication number
WO2003048935A1
WO2003048935A1 PCT/US2001/044941 US0144941W WO03048935A1 WO 2003048935 A1 WO2003048935 A1 WO 2003048935A1 US 0144941 W US0144941 W US 0144941W WO 03048935 A1 WO03048935 A1 WO 03048935A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
server
client device
boot
storage manager
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.)
Ceased
Application number
PCT/US2001/044941
Other languages
English (en)
Inventor
Jeffe And Bruce Bramhall Peter
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Symantec Operating Corp
Original Assignee
Veritas Operating Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Veritas Operating Corp filed Critical Veritas Operating Corp
Priority to AU2002241541A priority Critical patent/AU2002241541A1/en
Priority claimed from US09/998,246 external-priority patent/US6931558B1/en
Publication of WO2003048935A1 publication Critical patent/WO2003048935A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/1417—Boot up procedures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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

Definitions

  • the present invention generally relates to computers and local and wide area
  • NVRAM non-volatile memory
  • Boot disk, as well as other configurational set ups, are typically required. Boot disks and other set up tools are often not readily available in the location of each computer of a network or other wide area system. Moreover, to restore computer systems of such an
  • networks and system components of the networks particularly
  • the backups can include backup of
  • each computer of the enterprise network can be backed up regularly
  • An embodiment of the invention is a device restoration system.
  • the device
  • restoration system restores a client device to a state prior to a major failure.
  • server device includes a server device, a network communicatively interconnecting the client device
  • Another embodiment of the invention is a method of restoring a client device of a network on failure of the client device.
  • the network includes a server computer.
  • method includes booting the client device via a network or local media boot, creating a
  • boot program for operation on the client device, configuring the client device according to
  • the boot program and a saved configuration state, and copying files to the client device in accordance with a configuration from the step of configuring.
  • the network includes a server device.
  • the server device has a storage manager application.
  • the method includes backing up configuration data, as well as
  • the client device over the network.
  • FIG. 1 illustrates a network, including a client computer and a server computer
  • FIG. 2 illustrates a method of the restoration operation performed on the network
  • FIG. 3 illustrates the server computer, including components of a restore server, a
  • boot server a file server and a storage management server, and the client computer, each
  • FIG.1 according to embodiments of the present invention
  • FIG. 4 illustrates a method of restoration of a computer upon operational failure, according to embodiments of the present invention
  • FIG. 5 illustrates a method of operation of the server computer of FIGs. 1 and 3,
  • FIG. 6 illustrates a method of operation of the client computer of FIGs. 1 and 3,
  • a network 100 includes network elements 102 communicatively interconnecting a server computer 104 and a client computer 106.
  • network elements 102 include any of a wide variety of conventional networking
  • the server computer 104 is
  • any processing device that is communicatively connected by the network elements 102 to
  • the server computer 104 is, for example, a computer device
  • the server computer includes
  • 104 serves to receive requests over the network 100, for example, requests from the client
  • the server computer 104 is particularly capable of acting as a storage manager for interconnected elements and devices of the network or of
  • the client computer 106 of the network 100 is, likewise, any processing or communications device that is capable of communicating with the server computer 104
  • the client computer 106 is, for
  • the network 100 is any of a variety of networking and communications interconnections, such as an intranet, the Internet, a
  • the network 100 is operable according to a particular packetized data protocol, such as transport control
  • TCP/IP protocol/Internet protocol
  • the client computer 106 makes
  • server computer 104 responds over the network 100 in answer to the requests. If
  • the client computer 106 can not
  • the server computer 104 in conjunction with the client
  • This automatic restoration operation is performed without a boot disk at the client computer 106 and includes both system restoration and
  • a method 200 is performed by the server computer 104 and the
  • a command is run in a step 202 at the server computer 106 by the system administrator or other user of the server computer 106.
  • the step 202 initiates a network
  • the server computer 104 maintains, or otherwise has access to,
  • Such storage managers are a storage manager device or software application.
  • Such storage managers are
  • server devices such as the server computer
  • managers generally do not back up all files, but only back up application files and data.
  • Machine configuration states are not typically backed up.
  • present embodiments
  • the entirety of the client computer 106 is backed up by the storage manager, that is, all
  • configuration and file and data files of the client computer 106 can be incremental backups of only changed information since an immediately prior backup.
  • the server computer 104 of Fig. 1 includes four separate,
  • bare metal restore (BMR) server 302 a boot server 304
  • file server 306 a file server 306
  • SM storage manager
  • the boot server 304, the file server 306 and the SM server 308 is communicatively
  • the server components 300 are also communicatively connected to the BMR server 302.
  • the server components 300 are also communicatively connected to the BMR server 302.
  • server components 300 are illustrated in Fig. 3 as distinct and separate server
  • server components 300 are merely functions that can be performed and
  • the server components 300 can be each located on and performed by separate server
  • server devices can be grouped onto a single server device or combinations, banks, or other arrangements of server devices.
  • the server devices functioning as the server components
  • 300 can be centrally located or disparately located devices, all in communication over the
  • a method 400 restores the system and application and data
  • the method 400 is performed between the server components 300 and the client computer 106 over the network 100 and, thus, the restoration method 400 can be
  • the client device such as tape, CD-Rom, or floppy disk, serves to allow the client device 106 to boot from the server components 300 or media device, as applicable.
  • the server components 300 or media device as applicable.
  • server components 300 or media device, as applies, permits the client computer 106 to
  • the hard drive and other memory of the client computer 106 is
  • the server components 300 to reboot via communicated commands with the server
  • Remote re-boot and restoration can also occur according to the method 400, for example, in the case of a system like an ATX SP node, where the physical "front
  • computer 106 can be manipulated through software from another device, so that the
  • controlling device can electrically (and, if necessary, mechanically) initiate a reset as if
  • the method 400 is commenced in a step 402 at the BMR server 302 by a user, for
  • This run command of the step 402 causes the BMR server 302 to configure
  • the BMR server 302 retrieves configuration data regarding the client computer 106 from the
  • the configuration data so retrieved is the most recently backed up
  • the SM server 308 is a conventional storage manager application that serves to periodically backup and save application and file information present on the client
  • example of the storage manager application of the SM server 308 is the TSMTM software
  • manager applications include features enabling backups of client devices, such as
  • the storage manager backs up all of the client computer
  • this backup can be incremental with each
  • the BMR server 302 creates a client boot program and makes
  • the client boot program is delivered over the network 100 to the client
  • the boot image and file systems are saved at the boot server 304 and the file
  • the client computer 106 next is booted from the boot server 304 and runs the
  • client boot program to retrieve boot information from the boot server 304 and file systems from the file server 306 over the network 100.
  • the client computer 106 via network 100 communications between the client computer 106 and the file server 306, mounts configuration files from the file
  • client computer 106 is configured in a step 412, and appropriate disk configurations such
  • the client computer 106 uses the standard storage manager client application in a step 414 to restore files from the SM server 308 to the client computer 106.
  • standard storage manager client application is the client software or other application
  • the client computer 106 to communicate with the storage manager for backup and
  • the client computer 106 configures a boot record and configuration
  • the client computer -106 thereafter reboots, in
  • step 418 In a step 418. An added step 420 of post-boot clean-up can be required.
  • step 420 any client computer 106 settings and data that are not fully restored from
  • a step 502 is
  • the BMR server 302 retrieves or otherwise attains the appropriate disk structure for the particular client computer 106, for example, by retrieving such
  • step 506 follows, in which the format data is retrieved or otherwise attained of the disk
  • the format data is available through communications over the network 100 or otherwise as applicable.
  • the BMR server 302 creates a custom boot program for
  • the custom boot program includes information
  • triggered by the boot program is made through communications over the network 100 or
  • the BMR server 302 manipulates configuration of the boot server
  • the BMR server 302 prepares the respective server components 302, 304, 306, 308 and the client computer 106 for communications
  • a method 600 is performed by the client computer 106 to
  • the network boot is a standard
  • the client computer 106 communicates over the network 100 with the client computer 106.
  • the client computer 106 receives the client computer 106.
  • the client computer 106 next receives over the network 100 in a step 606 the
  • boot image for the client computer 106 from the boot server 304, and the boot image is copied to the client computer 106, for example, to random access memory (RAM).
  • RAM random access memory
  • the client computer 106 runs the customized boot program for the
  • the client computer 106 as obtained by the client computer 106 via communications over the network 100 from the BMR server 302.
  • step 610 mounts the system configuration files for the client computer 106
  • step 610 mounted to the client computer 106 from the file server 306 in the step 610 include the
  • the BMR server 302 over the network 100 to perform the restoration.
  • the hard disk of the client computer 106 is configured to match the
  • the client computer 106 communicates over the network 100 with the SM server 308 to recover from the
  • the client storage manager software that is, the typical client software that operates with the particular storage manager application to restore data from the storage manager
  • the step 612 could alternately involve communications with or by other
  • the client device 106 can in a Unix implementation instead communicate with
  • the client computer 106 configures its boot record from the
  • the step 620 can be
  • An auto boot of the client computer 106 then follows in a step
  • the step 622 is performed automatically by the client computer
  • server computer 104 and the client computer 106, it is to be
  • client devices such as the client computer 106 and others, as well as
  • server devices such as the server computer 104, its various server components 300, and
  • an intranet for example, be an intranet, even an intranet combination or intranet-extranet
  • a wide or local area network such as the Internet
  • a global network such as the Internet
  • the various devices can be disparately located and distributed, and can be can
  • network is capable of communicating by its protocols, which may include standard or

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé permettant de rétablir un dispositif client d'un réseau à la suite d'une défaillance majeure dudit dispositif, lequel est incapable de s'amorcer automatiquement. Le réseau comporte un ordinateur serveur. Le procédé consiste à amorcer le dispositif client sur le réseau lors de l'opération rétablissement, à configurer le dispositif client suivant le programme d'amorçage et les états de configuration sauvegardés relatifs audit dispositif, et à copier des fichiers sur le dispositif client conformément à la configuration. L'ordinateur client a accès à une application gestionnaire de mémoire, par exemple l'ordinateur serveur du réseau exploitant un programme gestionnaire de mémoire. Tous les fichiers client, y compris les fichiers configuration, ainsi que les fichiers application et données, du dispositif client sont sauvegardés sur le réseau par le biais de l'application gestionnaire de mémoire. Le dispositif client est amorcé sur le réseau, plutôt que localement vers le disque d'amorçage, notamment. Le programme d'amorçage est chargé sur le dispositif client, lequel extrait des informations de configuration et de fichiers sur le réseau à partir de l'application gestionnaire de mémoire. Le dispositif client configure son disque en fonction des informations de configuration; ensuite, tous les autres fichiers et données du dispositif client au moment de la défaillance de ce dernier sont sauvegardés sur le disque sensiblement dans les conditions et l'état avant la défaillance et comme les plus récemment récupérés vers l'application gestionnaire de mémoire. Dans un autre mode de réalisation, le dispositif client est remis en marche et amorcé par le biais d'un dispositif de commande relié notamment localement au dispositif client, et sensiblement en fonction du procédé d'amorçage du réseau.
PCT/US2001/044941 2001-11-29 2001-11-30 Systemes et procedes de retablissement d'ordinateurs Ceased WO2003048935A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002241541A AU2002241541A1 (en) 2001-11-29 2001-11-30 Computer restoration systems and methods

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/998,246 2001-11-29
US09/998,246 US6931558B1 (en) 2000-11-29 2001-11-30 Computer restoration systems and methods

Publications (1)

Publication Number Publication Date
WO2003048935A1 true WO2003048935A1 (fr) 2003-06-12

Family

ID=25544967

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/044941 Ceased WO2003048935A1 (fr) 2001-11-29 2001-11-30 Systemes et procedes de retablissement d'ordinateurs

Country Status (2)

Country Link
AU (1) AU2002241541A1 (fr)
WO (1) WO2003048935A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006035368A1 (fr) * 2004-09-29 2006-04-06 Philips Intellectual Property & Standards Gmbh Procede pour installer un programme logiciel sur un ordinateur
US7033582B2 (en) 2000-06-05 2006-04-25 Teva Pharmaceutical Industries, Ltd. Use of glatiramer acetate (copolymer 1) in the treatment of central nervous system disorders
GB2434888A (en) * 2006-02-02 2007-08-08 Hewlett Packard Development Co System for restoring a crashed client device by saving a configuration state to a server and creating a boot medium from the saved state.

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5452454A (en) * 1991-12-10 1995-09-19 Digital Equipment Corporation Generic remote boot for networked workstations by creating local bootable code image
US5828887A (en) * 1996-05-23 1998-10-27 Electronic Data Systems Corporation Network based program loader system and method of operation
US5930824A (en) * 1997-02-04 1999-07-27 International Business Machines Corporation System and method for demand-base data recovery
US6317826B1 (en) * 1998-02-13 2001-11-13 International Business Machines Corporation Booting a computer system from a network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5452454A (en) * 1991-12-10 1995-09-19 Digital Equipment Corporation Generic remote boot for networked workstations by creating local bootable code image
US5828887A (en) * 1996-05-23 1998-10-27 Electronic Data Systems Corporation Network based program loader system and method of operation
US5930824A (en) * 1997-02-04 1999-07-27 International Business Machines Corporation System and method for demand-base data recovery
US6317826B1 (en) * 1998-02-13 2001-11-13 International Business Machines Corporation Booting a computer system from a network

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7033582B2 (en) 2000-06-05 2006-04-25 Teva Pharmaceutical Industries, Ltd. Use of glatiramer acetate (copolymer 1) in the treatment of central nervous system disorders
WO2006035368A1 (fr) * 2004-09-29 2006-04-06 Philips Intellectual Property & Standards Gmbh Procede pour installer un programme logiciel sur un ordinateur
GB2434888A (en) * 2006-02-02 2007-08-08 Hewlett Packard Development Co System for restoring a crashed client device by saving a configuration state to a server and creating a boot medium from the saved state.
US7694169B2 (en) 2006-02-02 2010-04-06 Hewlett-Packard Development Company, L.P. Restoring a client device
GB2434888B (en) * 2006-02-02 2011-07-13 Hewlett Packard Development Co Restoring a client device

Also Published As

Publication number Publication date
AU2002241541A1 (en) 2003-06-17

Similar Documents

Publication Publication Date Title
US6931558B1 (en) Computer restoration systems and methods
US11675670B2 (en) Automated disaster recovery system and method
US6857011B2 (en) Method of remote imaging
US7281159B2 (en) Managing disk drive replacements on multidisk headless appliances
US8224784B2 (en) Combined computer disaster recovery and migration tool for effective disaster recovery as well as the backup and migration of user- and system-specific information
US7181646B2 (en) Mapping apparatus for backup and restoration of multi-generation recovered snapshots
JP4400913B2 (ja) ディスクアレイ装置
US7096381B2 (en) On-the-fly repair of a computer
US7680957B1 (en) Computer system configuration representation and transfer
US7694169B2 (en) Restoring a client device
US7849360B2 (en) Computer system and method of controlling communication port to prevent computer contamination by virus or malicious code
EP3705999B1 (fr) Procédé de mise à niveau de micrologiciel dans un système de stockage de n uds multiples
US20050034122A1 (en) Process, apparatus, and system for automatic system backup and restore during software installation
US7496783B1 (en) Merging cluster nodes during a restore
US7124322B1 (en) System and method for disaster recovery for a computer network
CN101909087A (zh) 一种基于快照的应用服务器远程引导方法
US7555674B1 (en) Replication machine and method of disaster recovery for computers
KR20040047209A (ko) 네트워크 상의 컴퓨터 시스템의 자동 복구 방법 및 이를구현하기 위한 컴퓨터 시스템의 자동 복구 시스템
WO2003048935A1 (fr) Systemes et procedes de retablissement d'ordinateurs
JP2008511910A (ja) ブート・ディスク管理のユティリティ
US7539899B1 (en) Cloning machine and method of computer disaster recovery
EP3629180B1 (fr) Procédé et système de restauration fiable de machines virtuelles
Clarke Backup and Recovery
Bach et al. Recovering Exadata
PURUSH et al. System Recovery

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP