Patent Application
20100115333
Computer systems may periodically need to be restored, for example in the event of a crash on a disk drive. Computer systems may periodically update their drivers to accommodate new devices in the network environment. However, in the event that a system restore operation is implemented on the computer system, updates to the drivers available on the computer system will be lost, which potentially reduces the ability of the computer system to interoperate with other devices in the network environment.
Described herein are exemplary systems and methods for dynamic driver loading for recovery boot media which may be implemented in a computer system. The methods described herein may be embodied as logic instructions stored on a computer-readable medium. When executed on a processor, the logic instructions cause a general processor to be programmed as a special-purpose machine that implements the described methods. The processor, when configured by the logic instructions to execute the methods recited herein, constitutes structure for performing the described methods.
In the embodiment depicted in
A file store 180 is communicatively connected to computer 108. File store 180 may be internal such as, e.g., one or more hard drives, or external such as, e.g., one or more external hard drives, network attached storage, or a separate storage network. File store 180 comprises one or more partitions 182, 184, 186.
Memory 130 includes an operating system 140 for managing operations of computer 108. In one embodiment, operating system 140 includes a hardware abstraction layer 154 that provides an interface to system hardware 120. In addition, operating system 140 includes a kernel 144, one or more file systems 146 that manage files used in the operation of computer 108 and a process control subsystem 148 that manages processes executing on computer 108. Operating system 140 further includes one or more device drivers 150 and a system call interface module 142 that provides an interface between the operating system 140 and one or more application modules 162 and/or libraries 164. The various device drivers 150 interface with and generally control the hardware installed in the computer system 100.
In operation, one or more application modules 162 and/or libraries 164 executing on computer 108 make calls to the system call interface module 142 to execute one or more commands on the computer's processor. The system call interface module 142 invokes the services of the file system(s) 146 to manage the files required by the command(s) and the process control subsystem 148 to manage the process required by the command(s). The file system(s) 146 and the process control subsystem 148, in turn, invoke the services of the hardware interface module 154 to interface with the system hardware 120. The operating system kernel 144 can be generally considered as one or more software modules that are responsible for performing many operating system functions.
The particular embodiment of operating system 140 is not critical to the subject matter described herein. Operating system 140 may be embodied as a UNIX operating system or any derivative thereof (e.g., Linux, Solaris, etc.), a Windows® brand operating system, or any other operating system.
Computer system 100 further includes a basic input/output system (BIOS) 126. In one embodiment, BIOS 126 may be implemented in flash memory and may comprise a power-on self-test (POST) module for performing system initialization and tests. In operation, when activation of computer system 100 begins, processing unit 122 accesses BIOS 126 and shadows the instructions of BIOS 126, such as power-on self-test module, into operating memory. Processor 122 then executes power-on self-test operations to implement POST processing.
In some embodiments, memory 130 includes a detection module 164 and a restore module 166 to implement dynamic driver loading for recovery boot media. In the embodiment depicted in
Referring to
At operation 210, detection module 164 retrieves driver(s) and other file(s) necessary to communication via the detected network interface hardware devices detected in operation 205. In some embodiments, the drivers and other file(s) may be retrieved from the computing device. In alternate embodiments the driver(s) may be retrieved from a remote source. For example, the detection module 164 may retrieve information identifying the computing device, then use the information to retrieve the driver(s) and other files from a remote source, e.g., from the manufacturer of the device via the Internet.
Once the driver(s) and other file(s) have been retrieved, they are stored on a persistent storage media. In some embodiments, the driver(s) and file(s) may be stored on a portion of the storage media 180 managed by the network attached storage device. By contrast, in some embodiments, the driver(s) and file(s) may be stored on an external storage media, e.g., a recover boot media 190 such as a recordable CD-ROM, a magnetic storage media, or an NV-RAM device.
At operation 220 the driver(s) and file(s) are linked to a restore library. By way of example, the driver(s) and file(s) may be logically linked to a library used by a restore application during a restore operation for the network attached storage device.
At operation 305 a system restore procedure is initiated. In some embodiments, the system restore procedure may be initiated by a user of the computer system 100, typically in response to a failure of a component (e.g., a hard drive) of the computer system 100.
At operation 310 the driver(s) and file(s) stored on the persistent storage media are retrieved, and at operation 315 the driver(s) and file(s) are utilized on the computer system 100 during the restore operation.
Some embodiments may be provided as computer program products, which may comprise a machine-readable or computer-readable medium having stored thereon instructions used to program a computer (or other electronic devices) to perform a process discussed herein. The machine-readable medium may comprise, but is not limited to, floppy diskettes, hard disk, optical disks, CD-ROMs, magneto-optical disks, ROMs, RAMs, erasable programmable ROMs (EPROMs), electrically erasable EPROMs (EEPROMs), magnetic or optical cards, flash memory, or other suitable types of media or computer-readable media suitable for storing electronic instructions and/or data. Moreover, data discussed herein may be stored in a single database, multiple databases, or otherwise in select forms (such as in a table).
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is comprised in at least an implementation. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
