US20060271819A1 - Recovering a system that has experienced a fault - Google Patents

Recovering a system that has experienced a fault Download PDF

Info

Publication number
US20060271819A1
US20060271819A1 US11497698 US49769806A US2006271819A1 US 20060271819 A1 US20060271819 A1 US 20060271819A1 US 11497698 US11497698 US 11497698 US 49769806 A US49769806 A US 49769806A US 2006271819 A1 US2006271819 A1 US 2006271819A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
system
network
software
fault
backup
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.)
Abandoned
Application number
US11497698
Inventor
Scott Cluff
Raymond Thorn
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.)
Mei California Inc
Original Assignee
Mei California Inc
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

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1417Boot up procedures
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1456Hardware arrangements for backup
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1469Backup restoration techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1464Management of the backup or restore process for networked environments

Abstract

A method and system of recovering a system that has experienced a fault includes a backup device to enable access of a network through the interface in response to the fault. The system includes a main operational portion that controls operation of the system under normal conditions. However, if a fault occurs, then the backup device can be selected to take over control of the system so that data can be retrieved from a backup storage to recover the system. The backup device includes software and/or hardware components to enable the system to access a network even though the main operational portion may not be functioning properly.

Description

    CROSS-REFERENCE TO RELATED APPLICATION
  • This is a continuation of U.S. patent application Ser. No. 09/706,960, entitled “Recovering a System that has Experienced a Fault,” filed Nov. 6, 2000, now U.S. Pat. No. 7,089,449, which is hereby incorporated by reference.
  • TECHNICAL FIELD
  • The invention relates to recovery of systems that have experienced faults.
  • BACKGROUND
  • Improvements in technology have provided users with a wide variety of devices to perform various tasks. Examples of such devices include desktop computer systems, portable computer systems, personal digital assistants (PDAs), mobile telephones, and so forth. The devices are relatively sophisticated devices that include processing elements (e.g., microprocessors or microcontrollers) and storage devices (e.g., hard disk drives, dynamic random access memorys or DRAMs, and so forth).
  • A typical device includes an operating system (e.g., a WINDOWS® operating system, a UNIX operating system, a LINUX operating system, etc.) that is loaded when the device is started. Application software is also loaded into the device to provide useful functions for users. Example applications include word processing applications, electronic mail applications, web browsing applications, calendar and address book applications, and so forth.
  • Despite improvements in technology, failures in various components of a device remains a persistent problem. When a component of a device, such as a hard disk drive, fails, the user may be left with an inoperational device. One option for the user is to take the device to a repair shop where an attempt may be made to recover the failed component, such as the failed hard disk drive. In some cases, data on the hard disk drives may be recovered so that loss of data is minimized. However, in many other cases, the data stored on the hard disk drive is lost, unless the user has diligently backed up the data.
  • Conventionally, recovery of the failed component such as the hard disk drive is an arduous process that often is frustrating for the user. A need thus exists for an improved method and apparatus for recovering a device to an operational state after a failure has occurred.
  • SUMMARY
  • In general, according to one embodiment, a system comprises an interface to a network and a first operational element to perform one or more tasks in the system. A storage element contains a flag to indicate if a fault has occurred with the first operational element. A backup device enables access to the network through the interface in response to the flag indicating failure of the first operational element.
  • In general, according to another embodiment, a system comprises a main storage device, a backup storage device, and a routine executable to boot from the backup storage device in case of a system fault. The backup storage device enables access over a network to retrieve data from a network node to recover the system.
  • Other features and embodiments will become apparent from the following description, from the claims, and from the drawings.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is an embodiment of a network system including a network, various nodes coupled to the network, and a backup storage system.
  • FIG. 2 is a block diagram of components of a node of FIG. 1, in accordance with an embodiment.
  • FIG. 3 is a flow diagram of tasks performed for a failure recovery in the node of FIG. 2, in accordance with an embodiment.
  • DETAILED DESCRIPTION
  • In the following description, numerous details are set forth to provide an understanding of the present invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these details and that numerous variations or modifications from the described embodiments may be possible.
  • Referring to FIG. 1, a network system 10 includes a network 12 that is coupled to network nodes 14, 16, and 18. Examples of the nodes 14, 16, and 18 include desktop computer systems, portable computer systems, and other types of systems having access to the network 12 (over either wired or wireless connections). Examples of the network 12 include local area networks (LANs), wide area networks (WANs), the Internet, and so forth.
  • A backup storage system 20 accessible over the network 12 stores data to be used to recover nodes 14, 16, and 18 in case of a fault (such as a component experiencing an error or failure) occurring in the nodes. The data stored in the backup storage system 20 includes user data, such as user-created documents or files, electronic mail messages, calendar and address book files, and so forth. The data stored in the backup storage system also includes software, such as operating system and application software that are stored and executed in each of the nodes. In one embodiment, the user data and software are stored as image data 30, 32, and 34 that correspond to nodes 14, 16, and 18, respectively. Thus, in case of a fault in node 14, the image data 30 is retrieved from the backup storage system 20 and communicated to the node 14, with the image data used to recover the node 14. Similarly, image data 32 and 34 are used to recover nodes 16 and 18, respectively.
  • As illustrated, the node 18 includes a main hard disk drive 24, a backup storage device 22, and a backup routine 26 executable in the node 18. The backup routine 26 is initially stored on the backup storage device 22 and is executable to enable the node 18 to access the backup storage system 20 over the network 12 in case one of several predetermined faults occurs in the node 18. Examples of such predetermined faults include failure of the hard disk drive, an unrecoverable error occurring on the hard disk drive, corrupted software and files associated with the software (e.g., library files, etc.), and so forth. The backup routine 26 and the backup storage device 22 may be collectively be referred to as the “backup device 25.” In the illustrated embodiment, the backup routine 26 is a software routine loaded from the backup storage device 22 for execution on a processing element in the node 18. Alternatively, the backup device is a hardware component that performs backup tasks in response to detection of certain types of faults.
  • More generally, the node 18 includes a main operational portion, which in one embodiment contains the main hard disk drive 24 (or some other type of storage element). The main operational portion controls operation when the node 18 functions normally. The main hard disk drive 24 stores the operating system and application software, which are loaded into the node 18 to perform useful tasks. In case of some predetermined faults, the backup device 25 is used to enable access over the network 12 to the backup storage system 20 to retrieve data to recover the main operational portion of the node 18.
  • The backup storage device 22 can be implemented in a number of different ways. For example, the backup storage device 22 can be a bootable mini-drive that is mounted inside the chassis of or on a motherboard in the node. The mini-drive can be a hard disk drive having a relatively small storage capacity for reduced cost. Alternatively, the mini-drive can be other types of non-volatile memory, such as flash memory, electrically erasable and programmable read-only memory (EEPROM) devices, and so forth. Instead of a separate component in the chassis of each node, the mini-drive can also be integrated onto the motherboard of the node if its size permits. Alternatively, the backup storage device 22 can be a full form factor drive.
  • The backup storage device 22 can also include a compact disk (CD) or digital video disk or digital versatile disk (DVD) drive in which a CD or DVD is loaded. The CD or DVD contains the necessary software to enable the node 18 to access the network 12. Alternatively, the backup storage device 22 includes a partition on the main hard disk drive 24. It is likely that only one part of the hard disk drive 24 is corrupted while another portion is not corrupted. The backup storage device 22 can also include other bootable cartridges or drives.
  • An example of the backup routine 26 is a browser that is capable of executing on a processor in each node to gain access to the network 12. To avoid having to load a large operating system such as the WINDOWS® operating system, the browser can be a reduced version browser that does not need standard full-scale computer operating systems to run. Examples of such “mini-browsers” include browsers that run in PDAs and other handheld devices. Alternatively, mini-browsers can be designed to operate in a DOS operating system, a WINDOWS® CE operating system, or other “lite” operating systems.
  • Referring to FIG. 2, an example of the node 18 (which has a similar arrangement as nodes 14 and 16) is illustrated. The node 18 includes a central processing unit (CPU) 100 that forms the processing core of the node 18. A host bridge 102 is connected over a host bus to the CPU 100. The host bridge 102 is also connected to a system bus 104, such as a Peripheral Component Interconnect (PCI) bus. Additionally, the host bridge 102 contains control elements to interface a main memory 103 and a video controller 116 that controls presentation of images on a display 114. The system bus 104 is connected to a network interface 112 that manages communications to the network 12 through a port 110.
  • Other components of the node 18 include a south bridge 123 coupled to the system bus 104. The south bridge 123 is in turn coupled to a disk controller 124 that is connected to the main disk drive 24. The disk controller 124 can also manage communications with a CD and/or DVD drive 126. An input/output (I/O) controller 118, which is connected to a floppy disk drive 120 and to a mini-drive 122, is also coupled to the south bridge 123.
  • When the node 18 first starts up, a basic input/output system (BIOS) routine 108 is loaded to perform boot and initialization tasks. The BIOS routine 108 is stored in a non-volatile memory 106, which can be a flash memory, EEPROM, and other like memory devices. Access to the non-volatile memory 106 is provided through the south bridge 123.
  • The backup storage device 22 of FIG. 1 can be one or more of the following elements in the node 18: the mini-drive 122, the CD or DVD drive 126, the floppy drive 120, the backup partition 130 in the main hard disk drive 24, or an additional drive like the main drive 24.
  • Although not shown, the node also includes various layers and stacks to enable communications over the network 12. For example, a network stack can include a TCP/IP (Transmission Control Protocol/Internet Protocol) or a UDP/IP (User Datagram Protocol/Internet Protocol) stack. TCP is described in RFC 793, entitled “Transmission Control Protocol,” dated September 1981; and UDP is described in RFC 768, entitled “User Datagram Protocol,” dated August 1980. One version of IP is described in Request for Comments (RFC) 791, entitled “Internet Protocol,” dated September 1981; and another version of IP is described in RFC 2460, entitled “Internet Protocol, Version 6 (IPv6) Specification,” dated December 1998. TCP and UDP are transport layers for managing connections over an IP network.
  • Also, various services enable the communication of requests over the network 12, such as requests between a node and the backup storage system 20. One such service is the Hypertext Transport Protocol (HTTP) service, which enables requests sent from one network element to another and responses from the destination network element to the requesting network element.
  • Referring to FIG. 3, the failure recovery process performed in one of the nodes 14, 16, and 18 is illustrated. The operating system 134 determines (at 202) if the node has experienced a fault. If so, the operating system 134 sets (at 204) a fail flag 132 (in the main hard disk drive 24) to an active state. Alternatively, the fail flag can be stored in the non-volatile memory 106, the mini-drive 122, or another memory storage element in the node.
  • Next, either in response to a user request to restart or automatically upon detection of the fault, the node is rebooted (at 206). When the node starts up, the BIOS routine 108 is loaded to perform boot tasks. One of the tasks performed by the BIOS routine 108 is to determine if the fail flag 132 has been set (at 208). If not, a normal boot process is performed (at 210) by the BIOS routine 108. If the fail flag 132 is set, then the BIOS routine 108 accesses (at 212) the backup storage device 22. Alternatively, instead of automatically checking for the fail flag 132, the boot from the backup storage device 22 can be performed manually by a user through the BIOS (such as by selecting the boot drive). Software on the storage device 22, including the backup routine 26, is loaded (at 214) into the node for execution on the CPU 100. As noted above, the backup routine 26 can be a mini-browser that enables communications over the network 12.
  • The backup routine 26 presents an indication of the fault (at 216), such as displaying a warning on the display 114. The backup routine 26 then waits (at 218) for a user request to recover. If a request to recover the node is received, then the backup routine 26 accesses (at 220) the remote backup system 20 over the network 12. Image data (30, 32, or 34) is retrieved from the backup storage system 20 and downloaded (at 222) into the node, where the image data is used to recover the node. A scan disk operation may be performed to determine portions of the hard disk drive that are defective. The image data can then be copied to the remaining portions of the hard disk drive 24 to enable normal operation of the node.
  • The various software routines or modules described herein may be executable on various processing elements. Such processing elements include microprocessors, microcontrollers, processor cards (including one or more microprocessors or microcontrollers), or other control or computing devices. As used here, a “controller” can refer to either hardware or software or a combination of the two.
  • The storage units include one or more machine-readable storage media for storing data and instructions. The storage media include different forms of memory including semiconductor memory devices such as dynamic or static random access memories (DRAMs or SRAMs), erasable and programmable read-only memories (EPROMs), electrically erasable and programmable read-only memories (EEPROMs), and flash memories; magnetic disks such as fixed, floppy and removable disks; other magnetic media including tape; or optical media such as CDs or DVDs. Instructions that make up the various software routines or modules when executed by a respective processing element cause the corresponding node to perform programmed acts.
  • The instructions of the software routines or programs are loaded or transported into the node in one of many different ways. For example, code segments including instructions stored on floppy disks, CD or DVD media, a hard disk, or transported through a network interface card, modem, or other interface device are loaded into the system and executed as corresponding software routines or modules. In the loading or transport process, data signals that are embodied in carrier waves (transmitted over telephone lines, network lines, wireless links, cables, and the like) communicate the code segments, including instructions, to the node. Such carrier waves may be in the form of electrical, optical, acoustical, electromagnetic, or other types of signals.
  • While the invention has been disclosed with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of the invention.

Claims (8)

  1. 1. A system comprising:
    a processor;
    an interface to a network;
    a BIOS routine executable on the processor;
    a storage element containing a flag to indicate if a fault has occurred in the system; and
    a backup device to enable access of the network through the interface,
    wherein the BIOS routine loads software from the backup device for execution on the processor in response to the flag indicating failure in the system,
    wherein the software is executable to access a remote backup storage over the network.
  2. 2. The system of claim 1, wherein the software is executable to retrieve image data from the backup storage, and wherein the image data is used to recover the system.
  3. 3. The system of claim 2, wherein the flag indicates if a fault has occurred with a disk drive, and wherein the software is executable to scan the disk drive to identify a first portion of the disk drive that is defective, and a second portion of the disk drive that is not defective, the software to store the image data to the second portion of the disk drive.
  4. 4. The system of claim 1, wherein the interface comprises a network stack having an Internet Protocol (IP) layer, wherein the backup device comprises a backup storage element containing the software adapted to perform communications through the network stack including the IP layer to the network.
  5. 5. The system of claim 4, wherein the software comprises a browser.
  6. 6. A method of performing error recovery in a system, comprising:
    detecting if an operating portion of the system has experienced a fault;
    setting a flag to indicate that the operating portion of the system has experienced a fault;
    during a boot process, a BIOS routine determining whether the flag is set;
    in response to determining the flag is set, accessing a backup device in the system to load software for execution;
    the software communicating through a network stack over a network to retrieve an image containing user data and an operating system.
  7. 7. The method of claim 6, further comprising recovering the system using the image.
  8. 8. The method of claim 6, wherein the software comprises a browser, and wherein the software communicating through the network stack over a network to retrieve the image is in response to a recover command received by the browser.
US11497698 2000-11-06 2006-08-02 Recovering a system that has experienced a fault Abandoned US20060271819A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US09706960 US7089449B1 (en) 2000-11-06 2000-11-06 Recovering a system that has experienced a fault
US11497698 US20060271819A1 (en) 2000-11-06 2006-08-02 Recovering a system that has experienced a fault

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US11497698 US20060271819A1 (en) 2000-11-06 2006-08-02 Recovering a system that has experienced a fault
US13294077 US20120060048A1 (en) 2000-11-06 2011-11-10 Recovering a system that has experienced a fault
US13612096 US20130067276A1 (en) 2000-11-06 2012-09-12 Software and methods for recovering a network node that has experienced a fault

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09706960 Continuation US7089449B1 (en) 2000-11-06 2000-11-06 Recovering a system that has experienced a fault

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13294077 Continuation US20120060048A1 (en) 2000-11-06 2011-11-10 Recovering a system that has experienced a fault

Publications (1)

Publication Number Publication Date
US20060271819A1 true true US20060271819A1 (en) 2006-11-30

Family

ID=36942149

Family Applications (4)

Application Number Title Priority Date Filing Date
US09706960 Active 2023-05-20 US7089449B1 (en) 2000-11-06 2000-11-06 Recovering a system that has experienced a fault
US11497698 Abandoned US20060271819A1 (en) 2000-11-06 2006-08-02 Recovering a system that has experienced a fault
US13294077 Abandoned US20120060048A1 (en) 2000-11-06 2011-11-10 Recovering a system that has experienced a fault
US13612096 Pending US20130067276A1 (en) 2000-11-06 2012-09-12 Software and methods for recovering a network node that has experienced a fault

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09706960 Active 2023-05-20 US7089449B1 (en) 2000-11-06 2000-11-06 Recovering a system that has experienced a fault

Family Applications After (2)

Application Number Title Priority Date Filing Date
US13294077 Abandoned US20120060048A1 (en) 2000-11-06 2011-11-10 Recovering a system that has experienced a fault
US13612096 Pending US20130067276A1 (en) 2000-11-06 2012-09-12 Software and methods for recovering a network node that has experienced a fault

Country Status (1)

Country Link
US (4) US7089449B1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7979690B1 (en) * 2008-05-06 2011-07-12 Acronis Inc. System and method for booting a computer from backup
US8145940B1 (en) 2002-10-09 2012-03-27 Rpx Corporation Method and system for updating a software image
US8336044B2 (en) 2002-10-09 2012-12-18 Rpx Corporation Method and system for deploying a software image
US9207871B2 (en) 2013-02-11 2015-12-08 Hewlett-Packard Development Company, L.P. Internal notebook microSD reader with read-only switch
US9542259B1 (en) * 2013-12-23 2017-01-10 Jpmorgan Chase Bank, N.A. Automated incident resolution system and method

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7593972B2 (en) * 2001-04-13 2009-09-22 Ge Medical Systems Information Technologies, Inc. Application service provider based redundant archive services for medical archives and/or imaging systems
JP2004361994A (en) * 2003-05-30 2004-12-24 Toshiba Corp Data management device, data management method and program
US20060023627A1 (en) * 2004-08-02 2006-02-02 Anil Villait Computing system redundancy and fault tolerance
US7370234B2 (en) * 2004-10-14 2008-05-06 International Business Machines Corporation Method for system recovery
US7930589B2 (en) * 2005-06-17 2011-04-19 Analog Devices, Inc. Interrupt-responsive non-volatile memory system and method
GB2431748B (en) * 2005-10-31 2010-12-22 Hewlett Packard Development Co Data back-up and recovery
US20070174689A1 (en) * 2005-11-23 2007-07-26 Inventec Corporation Computer platform embedded operating system backup switching handling method and system
US7565524B2 (en) * 2006-07-03 2009-07-21 Itzhak Levy Computer backup system at BIOS level
GB0620928D0 (en) * 2006-10-20 2006-11-29 Vodafone Plc Boot process
GB0620926D0 (en) 2006-10-20 2006-11-29 Vodafone Plc Group management
US7676503B2 (en) * 2006-11-27 2010-03-09 Microsoft Corporation Hybrid computer restore using network service
US8028158B1 (en) * 2008-07-10 2011-09-27 Cms Products, Inc. Method and apparatus for creating a self booting operating system image backup on an external USB hard disk drive that is capable of performing a complete restore to an internal system disk
JP5941273B2 (en) * 2011-12-02 2016-06-29 キヤノン株式会社 The information processing apparatus, and control method thereof

Citations (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4972316A (en) * 1987-03-30 1990-11-20 International Business Machines Corporation Method of handling disk sector errors in DASD cache
US5142680A (en) * 1989-04-26 1992-08-25 Sun Microsystems, Inc. Method for loading an operating system through a network
US5455933A (en) * 1993-07-14 1995-10-03 Dell Usa, L.P. Circuit and method for remote diagnosis of personal computers
US5469573A (en) * 1993-02-26 1995-11-21 Sytron Corporation Disk operating system backup and recovery system
US5513314A (en) * 1995-01-27 1996-04-30 Auspex Systems, Inc. Fault tolerant NFS server system and mirroring protocol
US5615330A (en) * 1994-11-12 1997-03-25 International Computers Limited Recovery method for a high availability data processing system
US5627964A (en) * 1994-12-13 1997-05-06 Microsoft Corporation Reduce or fail-safe bootstrapping of a system having a graphical user interface
US5713024A (en) * 1994-06-10 1998-01-27 Exabyte Corporation Cold boot data backup system
US5765151A (en) * 1995-08-17 1998-06-09 Sun Microsystems, Inc. System and method for file system fix-on-panic for a computer operating system
US5805882A (en) * 1996-07-19 1998-09-08 Compaq Computer Corporation Computer system and method for replacing obsolete or corrupt boot code contained within reprogrammable memory with new boot code supplied from an external source through a data port
US5905888A (en) * 1997-02-19 1999-05-18 On Spec Electronic, Inc. Bootable redundant hard disk attached to a PC's parallel port with rom-address auto-detect and configure during BIOS scan
US5974503A (en) * 1997-04-25 1999-10-26 Emc Corporation Storage and access of continuous media files indexed as lists of raid stripe sets associated with file names
US6016553A (en) * 1997-09-05 2000-01-18 Wild File, Inc. Method, software and apparatus for saving, using and recovering data
US6145088A (en) * 1996-06-18 2000-11-07 Ontrack Data International, Inc. Apparatus and method for remote data recovery
US6173417B1 (en) * 1998-04-30 2001-01-09 Intel Corporation Initializing and restarting operating systems
US6195695B1 (en) * 1998-10-27 2001-02-27 International Business Machines Corporation Data processing system and method for recovering from system crashes
US6314532B1 (en) * 1998-12-04 2001-11-06 Lucent Technologies Inc. Method and system for recovering from a software failure
US6324654B1 (en) * 1998-03-30 2001-11-27 Legato Systems, Inc. Computer network remote data mirroring system
US20020042892A1 (en) * 2000-10-06 2002-04-11 Stephen Gold Performing operating system recovery from external back-up media in a headless computer entity
US6374366B1 (en) * 1998-02-24 2002-04-16 Adaptec, Inc. Automated drive repair systems and methods
US6378086B1 (en) * 1997-02-24 2002-04-23 International Business Machines Corporation Method and system for recovering a computer system from a loadsource located at a remote location
US6381694B1 (en) * 1994-02-18 2002-04-30 Apple Computer, Inc. System for automatic recovery from software problems that cause computer failure
US6393585B1 (en) * 1998-12-23 2002-05-21 Scientific-Atlanta, Inc. Method and apparatus for restoring operating systems in a set-top box environment
US20020091710A1 (en) * 1999-11-10 2002-07-11 Scott Dunham Method for backup and restore of a multi-lingual network file server
US6446175B1 (en) * 1999-07-28 2002-09-03 Storage Technology Corporation Storing and retrieving data on tape backup system located at remote storage system site
US6535998B1 (en) * 1999-07-26 2003-03-18 Microsoft Corporation System recovery by restoring hardware state on non-identical systems
US6578160B1 (en) * 2000-05-26 2003-06-10 Emc Corp Hopkinton Fault tolerant, low latency system resource with high level logging of system resource transactions and cross-server mirrored high level logging of system resource transactions
US6625625B1 (en) * 1999-04-09 2003-09-23 Hitachi, Ltd. System and method for backup and restoring by utilizing common and unique portions of data
US6701450B1 (en) * 1998-08-07 2004-03-02 Stephen Gold System backup and recovery
US6799224B1 (en) * 1998-03-10 2004-09-28 Quad Research High speed fault tolerant mass storage network information server

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4910658A (en) * 1985-09-04 1990-03-20 Eaton Leonard Technologies, Inc. Real time process controller with serial I/O bus
US5390324A (en) * 1992-10-02 1995-02-14 Compaq Computer Corporation Computer failure recovery and alert system
US20020083361A1 (en) * 1996-01-04 2002-06-27 Compaq Information Technologies Group, L.P. Home base user interface
US6065073A (en) * 1998-08-17 2000-05-16 Jato Technologies, Inc. Auto-polling unit for interrupt generation in a network interface device
US6606716B1 (en) * 1999-10-06 2003-08-12 Dell Usa, L.P. Method and system for automated technical support for computers
US6738928B1 (en) * 2000-06-19 2004-05-18 Hewlett-Packard Development Company, L.P. Method and expert system for analysis of crash dumps

Patent Citations (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4972316A (en) * 1987-03-30 1990-11-20 International Business Machines Corporation Method of handling disk sector errors in DASD cache
US5142680A (en) * 1989-04-26 1992-08-25 Sun Microsystems, Inc. Method for loading an operating system through a network
US5469573A (en) * 1993-02-26 1995-11-21 Sytron Corporation Disk operating system backup and recovery system
US5455933A (en) * 1993-07-14 1995-10-03 Dell Usa, L.P. Circuit and method for remote diagnosis of personal computers
US6381694B1 (en) * 1994-02-18 2002-04-30 Apple Computer, Inc. System for automatic recovery from software problems that cause computer failure
US5713024A (en) * 1994-06-10 1998-01-27 Exabyte Corporation Cold boot data backup system
US5615330A (en) * 1994-11-12 1997-03-25 International Computers Limited Recovery method for a high availability data processing system
US5627964A (en) * 1994-12-13 1997-05-06 Microsoft Corporation Reduce or fail-safe bootstrapping of a system having a graphical user interface
US5513314A (en) * 1995-01-27 1996-04-30 Auspex Systems, Inc. Fault tolerant NFS server system and mirroring protocol
US5765151A (en) * 1995-08-17 1998-06-09 Sun Microsystems, Inc. System and method for file system fix-on-panic for a computer operating system
US6145088A (en) * 1996-06-18 2000-11-07 Ontrack Data International, Inc. Apparatus and method for remote data recovery
US5805882A (en) * 1996-07-19 1998-09-08 Compaq Computer Corporation Computer system and method for replacing obsolete or corrupt boot code contained within reprogrammable memory with new boot code supplied from an external source through a data port
US5905888A (en) * 1997-02-19 1999-05-18 On Spec Electronic, Inc. Bootable redundant hard disk attached to a PC's parallel port with rom-address auto-detect and configure during BIOS scan
US6378086B1 (en) * 1997-02-24 2002-04-23 International Business Machines Corporation Method and system for recovering a computer system from a loadsource located at a remote location
US5974503A (en) * 1997-04-25 1999-10-26 Emc Corporation Storage and access of continuous media files indexed as lists of raid stripe sets associated with file names
US6016553A (en) * 1997-09-05 2000-01-18 Wild File, Inc. Method, software and apparatus for saving, using and recovering data
US6374366B1 (en) * 1998-02-24 2002-04-16 Adaptec, Inc. Automated drive repair systems and methods
US6799224B1 (en) * 1998-03-10 2004-09-28 Quad Research High speed fault tolerant mass storage network information server
US6324654B1 (en) * 1998-03-30 2001-11-27 Legato Systems, Inc. Computer network remote data mirroring system
US6173417B1 (en) * 1998-04-30 2001-01-09 Intel Corporation Initializing and restarting operating systems
US6701450B1 (en) * 1998-08-07 2004-03-02 Stephen Gold System backup and recovery
US6195695B1 (en) * 1998-10-27 2001-02-27 International Business Machines Corporation Data processing system and method for recovering from system crashes
US6314532B1 (en) * 1998-12-04 2001-11-06 Lucent Technologies Inc. Method and system for recovering from a software failure
US6393585B1 (en) * 1998-12-23 2002-05-21 Scientific-Atlanta, Inc. Method and apparatus for restoring operating systems in a set-top box environment
US6625625B1 (en) * 1999-04-09 2003-09-23 Hitachi, Ltd. System and method for backup and restoring by utilizing common and unique portions of data
US6535998B1 (en) * 1999-07-26 2003-03-18 Microsoft Corporation System recovery by restoring hardware state on non-identical systems
US6446175B1 (en) * 1999-07-28 2002-09-03 Storage Technology Corporation Storing and retrieving data on tape backup system located at remote storage system site
US20020091710A1 (en) * 1999-11-10 2002-07-11 Scott Dunham Method for backup and restore of a multi-lingual network file server
US6578160B1 (en) * 2000-05-26 2003-06-10 Emc Corp Hopkinton Fault tolerant, low latency system resource with high level logging of system resource transactions and cross-server mirrored high level logging of system resource transactions
US20020042892A1 (en) * 2000-10-06 2002-04-11 Stephen Gold Performing operating system recovery from external back-up media in a headless computer entity

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8145940B1 (en) 2002-10-09 2012-03-27 Rpx Corporation Method and system for updating a software image
US8336044B2 (en) 2002-10-09 2012-12-18 Rpx Corporation Method and system for deploying a software image
US7979690B1 (en) * 2008-05-06 2011-07-12 Acronis Inc. System and method for booting a computer from backup
US8312259B1 (en) 2008-05-06 2012-11-13 Acronis International Gmbh System and method for booting a computer from backup
US9207871B2 (en) 2013-02-11 2015-12-08 Hewlett-Packard Development Company, L.P. Internal notebook microSD reader with read-only switch
US9542259B1 (en) * 2013-12-23 2017-01-10 Jpmorgan Chase Bank, N.A. Automated incident resolution system and method

Also Published As

Publication number Publication date Type
US7089449B1 (en) 2006-08-08 grant
US20120060048A1 (en) 2012-03-08 application
US20130067276A1 (en) 2013-03-14 application

Similar Documents

Publication Publication Date Title
US6678639B2 (en) Automated problem identification system
US6216226B1 (en) Method and system for dynamically selecting a boot process within a data processing system
US7100087B2 (en) Module and method for automatic restoring BIOS device
US6910160B2 (en) System, method, and computer program product for preserving trace data after partition crash in logically partitioned systems
US6931522B1 (en) Method for a computer using the system image on one of the partitions to boot itself to a known state in the event of a failure
US7305577B2 (en) Data isolation system and method
US6640317B1 (en) Mechanism for automated generic application damage detection and repair in strongly encapsulated application
US7043664B1 (en) Firmware recovery
US20050193189A1 (en) Device and method for booting an operating system for a computer from a passive directly attached network device
US6314455B1 (en) Data processing system and method for permitting a server to remotely initiate a client's boot block recovery
US6594709B1 (en) Methods and apparatus for transferring data using a device driver
US20090049295A1 (en) Determining a boot image based on a requesting client address
US7111202B2 (en) Autonomous boot failure detection and recovery
US5884073A (en) System and method for providing technical support of an electronic system through a web bios
US7487343B1 (en) Method and apparatus for boot image selection and recovery via a remote management module
US20040193865A1 (en) Secure online BIOS update schemes
US20050081118A1 (en) System and method of generating trouble tickets to document computer failures
US20060020858A1 (en) Method and system for minimizing loss in a computer application
US20040254978A1 (en) System and method of remotely accessing a computer system to initiate remote mainteneance and management accesses on network computer systems
US20040025155A1 (en) Method, computer program product, and system for configuring a software image for installation into a computer system
US20070169099A1 (en) Firmware update system for facilitating firmware update in mobile handset
US7096381B2 (en) On-the-fly repair of a computer
US20060026319A1 (en) Rollback of data
US8191078B1 (en) Fault-tolerant messaging system and methods
US6691225B1 (en) Method and apparatus for deterministically booting a computer system having redundant components

Legal Events

Date Code Title Description
AS Assignment

Owner name: MEI CALIFORNIA, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICRON ELECTRONICS, INC.;REEL/FRAME:029427/0284

Effective date: 20010322