US 5,922,072 AGrant

Method and Apparatus for Creating Alternate Boot Environments in a Computer

Issue Date:1999-07-13

•18 Claims

•4 Drawing Sheets

Abstract

The present invention discloses a method, apparatus, and article of manufacture for version migration and fallback of software components in a computer system. The invention creates alternate boot environments that preserve the state of all original software components on a system before performing a software upgrade. The invention virtually eliminates the risks of migrating to upgraded system because users can quickly fall back to a previous operating environment, without extended downtime during and after upgrades.

Metadata

Assignee

NCR Corporation

Inventors

Wayne Leslie Hutchinson
Gary Lee Boggs
David Neal Brinkman
Jeffrey Kittridge Janvrin

Application Information

Application Number:US 7785224

Filing Date:1997-01-03

Priority Date:1997-01-03

Art Unit:277

Classifications

IPC:

G06F 9445

Field of Search:

395713652;700;392;712;6002

Patent Drawings (4 sheets)

Description

BACKGROUND OF THE INVENTION

1. Field of Invention

The present invention generally relates to a method, apparatus, and article of manufacture for creating version migration and fallback for computer software. More specifically, this invention relates to a method for creating alternate boot environments that preserve the state of all original software components on a computer system before users perform a software upgrade.

2. Description of Related Art

Software products are perpetually upgraded with performance enhancements, new features, and problem corrections. These newer versions are released to computer users, but the user faces a risk of system failure when applying the software upgrade. Due to the inherent dependencies of computer hardware and software components, introducing a different version of a component into the system raises the possibility that a failure will occur. Such failures may range from a minor inconvenience to a catastrophic system failure. As a result, computer users risk extended downtime during and after upgrades, with no assurance of a complete fall-back strategy.

To create a fall-back strategy, users have long performed system backups, where all the files of a computer are copied to removable media such as tape. However, system recovery using such a scheme is very time consuming. Further, performing a recovery overwrites the previous system contents.

Thus, there is a need for an invention that eliminates the risks of migrating to an upgraded system and allows users to quickly fall back to a previous operating environment.

SUMMARY OF THE INVENTION

To overcome the limitations in the prior art described above, the present invention discloses a method and apparatus for version migration and fallback. More specifically, the present invention discloses a method for creating alternate boot environments in a computer system, comprising the following steps. Copying at least one software component from a first disk location to an alternate boot environment and updating this software component. Activating the updated software component at the alternate boot environment. Terminating the activated updated software component upon failure. Activating the software component at the first disk location after the terminating step.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers represent corresponding parts throughout:

FIG. 1 is a block diagram that illustrates an exemplary hardware environment of the present invention;

FIG. 2 is a flowchart showing the steps performed by the computer when a user creates alternate boot environments;

FIG. 3 is a representation of the computer responding to a user's command to copy original software components;

FIG. 4 is a representation of updated software components;

FIG. 5 illustrates a designated alternate boot environment; and

FIG. 6 is a representation of a system failure.

DETAILED DESCRIPTION OF THE INVENTION

In the following description, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present invention.

Overview

The present invention discloses a method for version migration and fallback of computer software that creates one or more alternative boot environments (ABE) on a computer system. More specifically, this invention allows a computer user to preserve the state of all original software components on a system before performing a software upgrade by copying the software to an alternative boot environment while maintaining an original copy of the software.

FIG. 1 is a block diagram that illustrates an exemplary hardware environment of the present invention. The present invention is typically implemented in a computer 10 that is comprised of a CPU 12, random access memory (RAM) 14, and other components. It is envisioned that attached to the computer 10 may be fixed data storage devices 16 (such as hard disk drives) and/or removable data storage devices 18 (such as CD-ROM drives, floppy disk drives, tape drives, etc.) and their associated media 20. Also included in the preferred embodiment may be other input and output devices such as, for example, network interfaces, monitors, printers, keyboards, etc.

Those skilled in the art will recognize that the exemplary environment illustrated in FIG. 1 is not intended to limit the present invention. Indeed, those skilled in the art will recognize that other alternative hardware environments may be used without departing from the scope of the present invention.

The computer 10 operates under the control of an operating system 24, such as the UNIX.TM., Windows.TM., Macintosh.TM., OS/2.TM., or other operating systems. The computer 10 executes one or more software applications 26 operating under the control of the operating system 24. The computer also executes one or more software update extensions 28 under the control of the operating system 24.

Generally, the operating system 24, the software application 26, and the software update extensions 28 are all tangibly embodied in a computer-readable medium, e.g., one or more of the fixed and/or removable data storage devices 16 and 18. The operating system 24, the software application 26, and the software update extensions 28 may be loaded from the data storage devices 14 and 16 into the random access memory 14 of the computer 10 for execution by the CPU 12. The operating system 24, the software application 26, and the software update extensions 28 all comprise instructions which, when read and executed by the CPU 12 of the computer 10, causes the computer 10 to perform the steps necessary to perform the method of the present invention.

The software update extension 28 is a software package of scripts, programs, and methodologies which provides a standardized way for software developers to release new versions of software components, e.g., the operating system 24 and/or software application 26. The primary advantage of the software update extension 28 is that it may be used to install or update the software components in a manner that increases availability of the computer 10. The software update extensions 28 may also include a fallback facility which maintain multiple versions of previously installed software components and allow a user to fallback to a previous version of the same software components.

In the present invention, the original software, e.g., the operating systems 24 and/or the software application, are copied from a first location on a data storage device 16 or 18 to a second location on the same or another data storage device 16 or 18. The copying step identifies all associated files of the original software components and copies these files to the ABE. Thereafter, the first location comprises an Original Boot Environment (OBE) and the second location comprises an Alternate Boot Environment (ABE). The software update extensions 28 are then applied to the ABE for version migration, leaving the OBE untouched. Therefore, in the event that the software components in the ABE somehow fail or do not work correctly, the OBE is preserved as a fallback.

Multiple instances of the ABE may be created for each subsequent version of the software update extensions 28. Further, the source for each ABE (be it the OBE or a previous ABE) may be designated as desired by the user. Thereafter, fallback may be selected from the currently active ABE to an earlier ABE or the OBE, as required.

Alternatively, upon completion of the ABE, a newer version of the software update extensions 28 may be applied to the OBE for version migration, with the ABE providing the fallback location. In this manner, the OBE subsequently becomes the new ABE and the ABE subsequently becomes the new OBE. Of course, this assumes that it is not necessary or desired to incorporate a new software update extension 28 being applied to the OBE with the intervening software update extension 28 previously applied to the ABE.

The present invention thus provides the capability of using the software update extensions 28 to either update currently active software components in a currently active ABE, or to update currently inactive software components in an inactive OBE or previous ABE. This invention allows users to select which ABE or OBE should be upgraded. This designated ABE may be active or inactive. The invention creates these updating options by limiting the scope of files and directories which can be accessed and/or modified by the software upgrade extension 28 so that only the software components in the designated ABE are affected by an upgrade.

On computers 10 with limited data storage resources (e.g., only one disk drive 16), the invention provides the ability to maintain multiple ABEs on a single "boot" disk. That is, a single disk drive 16 may contain two or more ABEs, each containing entirely different versions of the software components.

This invention further performs all the necessary modifications to the ABEs such that the computer 10 may boot from a designated ABE. Preferably, the invention allows a user to designate an active ABE and then updates the disk drive 16 so that the designated ABE will be used upon the next reboot of the computer 10.

In addition to providing a fallback from version migration, the present invention is a powerful tool for customizing the version migration. When creating an ABE, the user has the ability to customize the software components in the ABE through configuration options. The user can modify the file system layout to combine several file systems into one, or a single file system can be separated into multiple file systems on the ABE. The user can migrate to different size file systems and/or different file system types. For example, a current boot disk drive 16 may have all system files on a root file system. The user can modify this file system layout by separating the root file system into multiple file systems.

Creating Alternate Boot Environments

FIG. 2 is a flowchart illustrating the operation of computer 10 in accordance with the present invention.

Block 30 represents the computer 10 copying the original software components, e.g., the operating system 24 and/or the software application 26, from a first location on a first data storage device to a second location on the same or another data storage device. In most situations, the first location comprises the OBE and the second location comprises the ABE, although the first location may comprise an earlier ABE and the second location may comprise a later or subsequent ABE.

Block 32 represents the computer 10 updating the software components copied to the second location under the control of the software update extensions 28. After the update, two or more ABEs exist, wherein each contains entirely different versions of the software components.

Block 34 represents the computer 10 designating a desired ABE as the active ABE. Generally, the active ABE is the ABE at the second location, although this is under the control of the user.

Block 36 represents the computer 10 booting from the designated ABE and activating the software components on the designated ABE.

Block 38 is a decision block that represents the computer 10 determining whether a failure of some sort occurred in the booting of the designated ABE. If so, control transfers to Block 40, which represents the computer 10 switching back to the previous ABE or OBE and re-booting using the software components in the previous ABE or OBE. The invention executes Blocks 30 through 40 until a successful boot is achieved.

Block 42 represents the computer 10 executing the software from the designated ABE or OBE.

Original and Alternate Boot Environments

FIGS. 3, 4, 5, and 6 are block diagrams illustrating the structure of the original and alternate boot environments on one or more data storage devices according to the present invention.

In FIG. 3, the original boot environment (OBE) is designated as 44 and includes the original software components. One or more alternate boot environments (ABEs) are designated as 46 and include a copy of the original software components. These ABEs are created by the computer 10 responding to a user command to copy original software components 44 from a first location to a second location.

In FIG. 4, one of the ABEs designated by 48 is updated using the software update extensions 28. The updated ABE 48 may be designated as active or inactive. The invention creates this updating option by limiting the scope of files and directories which can be accessed and/or modified by the software upgrade extensions 28 so that only the designated ABE 48 is affected thereby.

In FIG. 5, the ABE 48 updated by the software update extensions 28 is designated as the active ABE 50. On computers 10 with limited data storage resources (e.g., only one disk drive 16), the invention supports the ability to maintain multiple ABEs on a single "boot" disk. That is, a single disk drive 16 may contain two or more ABEs, each containing entirely different versions of the software components. This invention further performs all the necessary modifications such that the computer 10 may boot from the designated ABE. As indicated above, the invention allows a user to designate the active ABE, and then updates the operating system 24 and/or the data storage device so that the selected ABE 50 will become active upon the next reboot of the computer 10.

In FIG. 6, the "X" through ABE 48 indicates a failure occurred as designated by 52. In response to the failure 52, a switch back to the OBE 44 as the active OBE is made (either manually or automatically) as designated by 50. The computer 10 is then re-booted from the newly designated active OBE 44.

Conclusion

This concludes the description of the preferred embodiment of the invention. In summary, the method involves creating alternate boot environments that preserve the state of all original software components on a system before performing a software upgrade.

The foregoing description of the preferred embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.

Claims

What is claimed is:

1. A method for creating alternate boot environments in a computer, comprising the steps of: (a) copying at least one software component from a first location on a first data storage device coupled to the computer to a second location on a second data storage device coupled to the computer; (b) updating the software components in the second location on the second data storage device; (c) booting the computer from the alternate boot environment by activating the updated software components at the second location on the second data storage device; (d) terminating the booting step when the activated updated software components fail to operate correctly; and (e) activating the software components at the first location on the first data storage device after the terminating step.

2. The method of claim 1 above, wherein the first location comprises an original boot environment and the second location comprises an alternate boot environment.

3. The method of claim 1 above, wherein the first location comprises a first alternate boot environment and the second location comprises a second alternate boot environment.

4. The method of claim 1 above, wherein the first data storage device is the second data storage device.

5. The method of claim 1 above, wherein the first data storage device is not the second data storage device.

6. The method of claim 1 above, further comprising the steps of identifying all files associated with the software components at the first location and copying the identified files from the first location to the second location.

7. An apparatus for creating alternate boot environments in a computer, comprising: (a) means, performed by the computer, for copying at least one software component from a first location on a first data storage device coupled to the computer to a second location on a second data storage device coupled to the computer; (b) means, performed by the computer, for updating the software components in the second location on the second data storage device; (c) means, performed by the computer, for booting the computer from the alternate boot environment by activating the updated software components at the second location on the second data storage device; (d) means, performed by the computer, for terminating the booting step when the activated updated software components fail to operate correctly; and (e) means, performed by the computer, for activating the software components at the first location on the first data storage device after the terminating step.

8. The apparatus of claim 7 above, wherein the first location comprises an original boot environment and the second location comprises an alternate boot environment.

9. The apparatus of claim 7 above, wherein the first location comprises a first alternate boot environment and the second location comprises a second alternate boot environment.

10. The apparatus of claim 7 above, wherein the first data storage device is the second data storage device.

11. The apparatus of claim 7 above, wherein the first data storage device is not the second data storage device.

12. The apparatus of claim 7 above, further comprising means for identifying all files associated with the software components at the first location and means for copying the identified files from the first location to the second location.

13. An article of manufacture for creating alternate boot environments, comprising the steps of: (a) copying at least one software component from a first location on a first data storage device coupled to the computer to a second location on a second data storage device coupled to the computer; (b) updating the software components in the second location on the second data storage device; (c) booting the computer from the alternate boot environment by activating the updated software components at the second location on the second data storage device; (d) terminating the booting step when the activated updated software components fail to operate correctly, and (e) activating the software components at the first location on the first data storage device after the terminating step.

14. The method of claim 13 above, wherein the first location comprises an original boot environment and the second location comprises an alternate boot environment.

15. The method of claim 13 above, wherein the first location comprises a first alternate boot environment and the second location comprises a second alternate boot environment.

16. The method of claim 13 above, wherein the first data storage device is the second data storage device.

17. The method of claim 13 above, wherein the first data storage device is not the second data storage device.

18. The method of claim 13 above, further comprising the steps of identifying all files associated with the software components at the first location and copying the identified files from the first location to the second location.

Patent Citations (24)

Patent	Date	Inventor
US4799145	1989-01-01	Goss et al.
US5053797	1991-10-01	Samuels et al.
US5155847	1992-10-01	Kirouac et al.
US5210854	1993-05-01	Beaverton et al.
US5247683	1993-09-01	Holmes et al.
US5257377	1993-10-01	Sathi et al.
US5274816	1993-12-01	Oka
US5280627	1994-01-01	Flaherty et al.
US5325532	1994-06-01	Crosswy et al.
US5355489	1994-10-01	Bealkowski et al.
US5355498	1994-10-01	Provino et al.
US5359730	1994-10-01	Marron
US5404508	1995-04-01	Konrad et al.
US5410703	1995-04-01	Nilsson et al.
US5421017	1995-05-01	Scholz et al.
US5469573	1995-11-01	McGill et al.
US5485606	1996-01-01	Midgdey et al.
US5579522	1996-11-01	Christeson et al.
US5664194	1997-09-01	Paulsen
US5675795	1997-10-01	Rawson, III et al.
US5701477	1997-12-01	Chejlava, Jr.
US5715456	1998-02-01	Bennet et al.
US5724536	1998-03-01	Abramson et al.
US5764992	1998-06-01	Kullick et al.

Abstract

Description