JP2005327216A - Method for starting os from hard disk image file - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method for starting an OS from a hard disk image file which can be started while holding environment which normally operates. <P>SOLUTION: The normal operation environment is preliminarily backed up including the OS, in the case of starting the backed up environment, the whole backup file is considered as an HDD having a boot sector and the environment is started not by a normally started OS but by a backup file. Thus, since normally used operation environment is also held, a user can optionally start both of the normal OS and the backup environment. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a method for booting an OS from a hard disk image file.

As a countermeasure against a conventional computer failure, as a simple method for backing up the contents of a hard disk (hereinafter referred to as HDD), the data of the HDD to be protected is recorded on a recording medium such as an HDD or CD-ROM of another computer. In this case, it is possible to record the information on the HDD at any time, reinstall the operating system (hereinafter referred to as OS) when a failure occurs, and then copy back the HDD data backed up. Japanese Patent Application Laid-Open No. 2004-228867 discloses a technique in which all files including an OS stored in an HDD are previously backed up to an external storage medium such as a CD-ROM, and the backup file is restored to the HDD for each OS when a failure occurs. It is disclosed.
JP 2003-308254 A

  However, the conventional backup method restores each OS by any method, and the current operating environment is deleted. Therefore, it is not possible to reproduce an environment that is backed up while maintaining the current operating environment. In addition, there is a problem that it takes time and effort to restore.

  In order to solve this problem, the present invention proposes a method of starting up an OS from a hard disk image file or the like. The feature of the present invention is that the normal operating environment including the OS is backed up, and when starting the backed up environment, the entire backup file is regarded as an HDD having a boot sector, and the OS that is normally started Instead, it starts with a backup file. As a result, the backed up environment can be operated while the normal operating environment is maintained.

  As described above, it is possible to backup the entire OS while maintaining the normal operating environment, and to arbitrarily start up the backup environment or start up the normal OS environment.

  Hereinafter, embodiments of the present invention will be described. Note that the present invention is not limited to these embodiments, and can be implemented in various modes without departing from the spirit of the present invention.

  In addition, the relationship between the following embodiment and a claim is as follows.

  The first embodiment will mainly describe claims 1, 2, 3, 7 and the like.

  The second embodiment will mainly describe claims 4, 5, 8 and the like.

The third embodiment will mainly describe claim 6 and the like.
<< Embodiment 1 >>

  <Outline of Embodiment 1>

  The present embodiment relates to a computer including a first storage area that holds an operating environment that starts from a normal OS and a second storage area that holds an operating environment that starts from a backup file.

  1 and 2 show an example of the concept of the present embodiment.

  FIG. 1 shows an operation when a normal OS is started. When the computer is turned on for the first time, a master boot record unit (0120) is read by a central processing unit (hereinafter referred to as a CPU) in accordance with a BIOS (Basic Input / Output System) (0110) instruction stored in a ROM. Thus, the boot program included in the master boot record portion (0120) operates. The boot program searches the active storage area (here, the first storage area), and the CPU reads the boot sector portion (0130) of the active storage area. (In other words, even if there is a file necessary for starting the OS in the inactive storage area, it is not read.) Furthermore, it is necessary for starting the OS by the program written in the boot sector (0130). A boot file included in the first boot file portion (0140), which is a simple file, is read and the OS is booted.

  FIG. 2 shows the operation when starting from a backup file. When starting from the backup file, as a preparation, a new new boot record part (0230) for starting from the backup file is written, and the CPU is instructed by the master boot record part (0220). Rewrite to read (0230). When the computer is turned on in this state, the master boot record portion (0220) is read by the CPU in accordance with the BIOS (0210) command stored in the ROM as in the normal state. Thereafter, the CPU normally reads the boot sector of the active storage area according to the instruction of the master boot record part (0220). In this case, the CPU is rewritten to read the newly added new boot record part (0230). Therefore, the new boot record part (0230) is read. Further, in response to an instruction from the new boot record part (0230), the CPU reads the backup file part (0250) which is a backup file of the first storage area stored in the second storage area. Alternatively, the address conversion table holding unit (0240) that performs address conversion for reading may be read once and then the backup file unit (0250) may be read. In this case, the address conversion table holding unit (0240) may be read. ) Is a table indicating where the requested information is located in the backup file part (0250). Therefore, when processing the information stored in the backup file part (0250), this is always performed. Access is made using a conversion table.

  As described above, according to the present invention, a storage area that has been active in the past, that is, a second storage area that is a new storage area without erasing files and the like that are stored in the first storage area and that are required for startup. The OS can be started from the area. Therefore, even if there is important information in the first storage area, it is convenient because the OS can be started up from another storage area while the state is saved without being deleted. Further, the first storage area and the second storage area may be in the same partition or in different partitions. Here, a partition is a unit of a storage area that is integrally recognized as a storage area by the master boot record portion (0220).

  <Configuration of Embodiment 1>

  An example of functional blocks in this embodiment is shown in FIG.

  The “computer” (0300) of this embodiment shown in FIG. 3 includes a “first storage area” (0310), a “second storage area” (0320), a “master boot record rewriting unit” (0330), A “new boot record adding unit” (0340) and an “address conversion table holding unit” (0350) are included. The first storage area (0310) includes a “master boot record portion” (0311), a “boot sector portion” (0312), a “first boot file portion” (0313), and a “new boot record portion” ( The second storage area (0320) is composed of a “backup file part” (0321).

  The “master boot record portion” (0311) is a portion on the HDD that is read first when the normal computer is started, and information for starting the OS is written at the top of the normal HDD. When the computer starts, first, a boot program included in the master boot record portion (0311) operates. The boot program reads information for searching for an active storage area, and reads a boot sector portion described later of the active storage area to be activated.

  The “boot sector portion” (0312) is a portion on the HDD that is read when a boot program operates in the master boot record portion (0311). The boot sector part (0312) of the active storage area to be activated is read, and the OS is activated by the program written here.

  The “first boot file portion” (0313) is a place where a boot file which is a file necessary for booting the OS booted by the boot sector portion (0312) is placed. The OS is started by the file existing here.

  The “new boot record part” (0314) is added to the first storage area (0310) by a new boot record addition part (to be described later), and when starting from a backup file, the master boot record part (0311) is added. ). This is for accessing a backup file portion of a second storage area described later.

  The “backup file portion” (0321) has a backup file of the file that has been arranged in the first storage area (0310). This includes not only data for starting the OS, but also user data in some cases.

  The “master boot record rewriting unit” (0330) has a function of rewriting the master boot record unit (0311) so as to read the new boot record unit (0314) in order to start up with a backup file.

  The “new boot record adding unit” (0340) adds the new boot record unit (0314) read from the master boot record unit (0311) to the first storage area (0310) when starting with the backup file. It has a function.

  The “address conversion table holding unit” (0350) stores a first address that is the address of the first storage area (0310) and a second address that is the address of the second storage area (0320) in association with each other. Have When booting from the backup file part (0321), the new boot record part (0314) is accessed. Thereafter, when the backup file portion (0321) is accessed, it is accessed each time for converting the first address and the second address. Further, as a means for converting the address, the first address and the second address can be converted by a mathematical formula or the like without using a conversion table.

  The master boot record rewriting unit (0330), the new boot record adding unit (0340), and the address conversion table holding unit (0350) may be in the first storage area (0310). It may be in the second storage area (0320). Further, it may be in another storage area.

  <Specific example of Embodiment 1>

  A specific example of this embodiment will be described. FIG. 4 shows an example of a specific example.

  When the computer is first turned on, the master boot record part (0411) of the first storage area (0410) is read by the CPU. The CPU reads the boot sector part (0412) of the first storage area (0410), which is an active storage area, when the normal OS is started up according to the instruction of the master boot record part (0411). The OS is activated by reading the activation file at the address (0413), for example, address “1000”. When booting from a backup file, the CPU reads the new boot record portion (0414) according to the rewritten instruction of the master boot record portion (0411). Further, when the startup file of the backup file unit (0421) is directly read according to the instruction of the new boot record unit (0414) or the startup file is accessed through the address conversion table holding unit (0450), for example, the address conversion table holding unit Since the location of the startup file in the backup file section (0421) is found at the address “2500” by associating the first address with the second address at (0450), the startup file at the address “2500” is accessed. Start up the OS. Thereafter, when reading the information in the backup file part (0421) to start the OS, the address translation table holding part (0450) is accessed to know the position of the information, and the information at that position is read. repeat.

  <Processing flow of Embodiment 1>

  FIG. 5 shows the flow of processing at the time of normal OS startup. 6, 7, and 8 show the flow of processing when booting from a backup file, FIG. 6 shows the flow of pre-processing for booting from a backup file, and FIGS. 7 and 8 are boot files. This is a flow of processing when starting the reading of the backup file directly when starting to read the file, and when starting reading after performing address conversion by the address conversion table holding unit.

  The process shown in FIG. 5 includes the following steps.

  First, the master boot record portion is read (master boot record portion reading step S0510).

  Next, information for specifying an active storage area written in the master boot record part read in the master boot record part reading step (S0510) is acquired (active storage area information acquisition step S0520).

  Next, the boot sector part of the active storage area acquired in the active storage area information acquisition step (S0520) is read by the CPU (boot sector part reading step S0530).

  Finally, the boot file necessary for booting the OS is read by the CPU according to the instruction of the boot sector portion read in the boot sector portion reading step (S0530) (boot file reading step S0540).

  The process shown in FIG. 6 includes the following steps.

  First, a new boot record part is added by the new boot record addition part (new boot record part addition step S0610).

  Next, the master boot record rewriting unit rewrites the master boot record unit so that the CPU reads the new boot record unit added by the new boot record unit adding step (S0610) (master boot record unit rewriting step S0620).

  Further, the process shown in FIG. 7 includes the following steps.

  First, the CPU reads the master boot record portion rewritten by the master boot record rewriting portion (master boot record portion reading step S0710).

  Next, information for specifying a storage area to be read is acquired from the master boot record part read in the master boot record part reading step (S0710) (storage area information acquisition step S0720).

  Next, the new boot record part of the storage area acquired in the storage area information acquisition step (S0720) is read by the CPU (new boot record part reading step S0730).

  Next, the CPU reads the boot file included in the backup file portion according to the instruction of the new boot record portion read in the new boot record portion reading step (S0730) (boot file reading step S0740).

  Next, in order to start with a backup file, if there is further data to be read, the address conversion table holding unit performs address conversion (address conversion step S0760), and the start file reading step (S0740) is repeated. Further, after the activation file is read, the application is similarly activated (reading continuation determination step S0750).

  8 is different from that in FIG. 7 in that the address conversion table is used when the CPU starts reading the boot file included in the backup file portion after the new boot record portion reading step (S0830 in FIG. 8). The difference is that the address file is once converted by the holding unit (S0840) and the start-up file is read (S0850). The other steps are the same as in FIG.

  The above processing can be executed by a program for causing a computer to execute, and the program can be recorded on a recording medium readable by the computer. (The same applies throughout the specification.)

  <Effect of Embodiment 1>

As described above, the computer according to the present embodiment provides a mechanism for operating a backup file while maintaining the operating environment used by the user during normal operation. The user arbitrarily starts a normal OS. Or can be activated by a backup file.
<< Embodiment 2 >>

  <Outline of Embodiment 2>

  A feature of the computer according to the present embodiment is that when a rewrite request is made to rewrite a data storage area included in a startup file when the computer is started from a backup file, the rewrite process is not performed by saving the rewrite process to a predetermined storage area. It has a function. The rewriting process means a process of writing information in the registry when the OS is started. Further, since the rewrite process is saved in a predetermined storage area, the saved rewrite process information can be saved so as to be reusable when activated from the backup file.

  <Configuration of Embodiment 2>

  An example of functional blocks in the present embodiment is shown in FIG.

  The “computer” (0900) of this embodiment shown in FIG. 9 includes a “first storage area” (0910), a “second storage area” (0920), a “master boot record rewriting unit” (0930), “New boot record adding unit” (0940), “Address conversion table holding unit” (0950), “Protector unit” (0960), “Predetermined storage area” (0970), and “Saved file reuse unit” (0980). The configuration other than the protector unit (0960), the predetermined storage area (0970), and the save file reuse unit (0980) is the same as that of the first embodiment.

  The “protector unit” (0960) has a function of saving a rewrite process to a predetermined storage area (to be described later) when a rewrite process is requested for the data storage area included in the backup file when the backup file is activated. Specific examples of the rewriting process include a process of registering information related to hardware connected when the computer is started up in a registry, and a process of rewriting information related to an application. With these functions, the data storage area can be prevented from being rewritten, and the saved data can be read to make it appear as if it has been rewritten while starting from the backup file.

  The “predetermined storage area” (0970) is an area where the protector unit (0960) saves the rewrite processing for the data storage area included in the backup file. The place where the predetermined storage area is placed may be in the same partition as the backup file unit (0921) or in a different partition.

  The “save file reuse unit” (0980) has a function of saving the rewrite processing information saved in the predetermined storage area (0970) so as to be reusable when activated from the backup file. With this function, the saved rewrite processing information can be reflected in the backup file. As a method of reflecting, there is a method to save the saved rewrite processing information in the backup file, or to read the saved rewrite processing information without saving directly, as if the backup file was rewritten it can.

  <Specific example of Embodiment 2>

  A specific example of this embodiment will be described. FIG. 10 shows an example of a specific example.

  The feature point of the computer of this embodiment is that it has a function of saving the rewrite process to a predetermined storage area when a rewrite process for rewriting the data storage area included in the startup file part of the back file part occurs. The process will be described in detail.

  The backup file stored in the backup file portion (1010) includes a startup file for starting up the OS. When the normal OS is booted, a process of writing information such as a registry to the boot file occurs. In the present embodiment, the rewrite process file executes the rewrite process in the location where the data storage area writes. When the rewrite process is generated by the rewrite process file, the rewrite process is saved in the predetermined storage area (1030) by the protector unit (1020) so that the data storage area is not rewritten. Thereafter, the saved file reusing unit (1040) can save the rewritten processing information saved so as to be reusable when activated from the backup file.

  <Processing flow of Embodiment 2>

  FIG. 11 shows an example of the flow of processing when a rewrite request is generated in the second embodiment.

  The process shown in FIG. 11 includes the following steps.

  First, a rewrite request to the backup file unit is generated (rewrite request generation step S1110).

  Next, the rewrite process for the rewrite request generated in the rewrite request generation step (S1110) is saved in a predetermined storage area (rewrite process save step S1120).

  Next, by reading the rewrite process saved in the predetermined storage area in the rewrite process saving step (S1120), it operates as if the predetermined storage area was actually rewritten. Alternatively, the saved rewrite processing information is stored so as to be reusable when activated from the backup file. (Spoofing execution processing step S1130)

  <Effect of Embodiment 2>

As described above, the computer according to the present embodiment has a function of saving the rewriting process required when the OS is started up to another area, so that the backup file can be maintained at the time when the backup file is backed up without performing the rewriting process. Can do. Further, the saved rewrite processing information can be saved so as to be reusable when activated from the backup file.
<< Embodiment 3 >>

  <Outline of Embodiment 3>

  A feature of the computer according to the present embodiment is that it has a function of executing a rewrite process when a rewrite request for rewriting the data storage area included in the startup file is made when the backup file is activated.

  <Configuration of Embodiment 3>

  An example of functional blocks in this embodiment is shown in FIG.

  The “computer” (1200) of this embodiment shown in FIG. 12 includes a “first storage area” (1210), a “second storage area” (1220), a “master boot record rewriting unit” (1230), A “new boot record adding unit” (1240), an “address conversion table holding unit” (1250), and a “rewrite processing execution unit” (1260) are included. The configuration other than the rewrite processing execution unit (1260) is the same as that of the first embodiment.

  The “rewrite processing execution unit” (1260) has a function of executing a rewrite process when a rewrite process is requested for the data storage area included in the backup file when the backup file is activated. The rewrite processing execution unit may be in the first storage area (1210) or in the second storage area (1220). Further, it may be in another storage area.

  <Processing flow of Embodiment 3>

  FIG. 13 shows an example of the flow of processing when a rewrite request occurs in the third embodiment.

  The process shown in FIG. 13 includes the following steps.

  First, a rewrite request to the backup file unit is generated (rewrite request generation step S1310).

  Next, a rewrite process for the rewrite request generated in the rewrite request generation step (S1310) is executed (rewrite process execution step S1320).

  <Effect of Embodiment 3>

  As described above, in the computer according to the present embodiment, when a rewrite request is generated for the data storage area included in the backup file when the backup file is activated, the rewrite process can be executed.

Conceptual diagram for explaining the first embodiment (starting from a normal OS) Conceptual diagram for explaining the first embodiment (starting from a backup file) Functional block diagram for explaining the first embodiment Specific example for explaining the first embodiment FIG. 3 is a diagram for explaining a processing flow according to the first embodiment (starting from a normal OS); Diagram for explaining the flow of processing in Embodiment 1 (preparation for backup file activation) Diagram for explaining the flow of processing in Embodiment 1 (when a backup file is activated) Diagram for explaining the processing flow of Embodiment 1 (when a backup file is activated) Functional block diagram for explaining the second embodiment Specific example for explaining the second embodiment The figure explaining the flow of processing of Embodiment 2. Functional block diagram for explaining the third embodiment The figure explaining the flow of processing of Embodiment 3.

Explanation of symbols

0210 BIOS
0220 Master boot record part 0230 New boot record part 0240 Address conversion table holding part 0250 Backup file part

Claims (8)

A computer that arranges a master boot record portion, a boot sector portion, and a first boot file portion having a boot file to be read by the boot sector portion in a first storage area,
A new boot record adding unit that adds a new boot record unit that functions in place of the boot sector unit to the first storage area;
Rewriting the master boot record portion, and causing the BIOS to read the new boot record portion instead of the boot sector portion, a master boot record rewriting portion;
A backup file part having a backup file of a file originally included in the first storage area and including a startup file designated to be read from the new boot record part in the second storage area;
When a file included in the backup file is arranged in the first storage area, a first address that is an address indicated by an instruction based on the file and the backup file in the second storage area are arranged. An address conversion table holding unit that holds the second address associated with the second address,
Having a calculator.   The computer according to claim 1, wherein the first storage area and the second storage area are arranged in the same partition.   The computer according to claim 1, wherein the first storage area and the second storage area are arranged in different sections. The startup file has a rewriting process file for executing a rewriting process for rewriting a data storage area included in the startup file at the time of startup,
When the new boot record unit is activated by the start-up file of the backup file, the rewrite process of the rewrite process file is saved in a predetermined storage area and the rewrite process for the data storage area included in the start-up file of the backup file is executed. The computer as described in any one of Claim 1 to 3 which has a protector part for not doing.   The computer according to claim 4, further comprising a save file reuse unit that saves the saved rewrite processing information so as to be reusable when activated from the backup file. The startup file has a rewriting process file for executing a rewriting process for rewriting a data storage area included in the startup file at the time of startup,
A rewrite process execution unit for executing rewrite processing of the rewrite process file on a data storage area included in the start file of the backup file when the new boot record unit is activated by the boot file of the backup file; The computer according to any one of claims 1 to 3. A backup method for a computer having, in a first storage area, a master boot record portion, a boot sector portion, a startup file to be read by the boot sector portion, and an application file used in a state where the boot file is started Because
A new boot record adding step for adding a new boot record portion functioning instead of the boot sector portion to the first storage area;
A master boot record rewriting step for rewriting the master boot record portion and causing the BIOS to read the new boot record portion instead of the boot sector portion;
A backup step of copying a backup file of a file originally included and used in the first storage area, including a boot file designated to be read from the new boot record section in the second storage area;
When the file included in the backup file is located in the first storage area, the backup file in the second storage area is assigned the first address that is the address pointed to by the instruction based on the file. An address translation step for converting to a second address,
A computer backup method. A computer backup method originally having a rewriting process for rewriting a data storage area included in the startup file when the startup file is started,
When the boot file of the backup file is activated by the new boot record section, the rewriting process of the rewriting process file is saved in a predetermined storage area and the rewriting process for the data storage area included in the boot file of the backup file is executed. A protector part generation step for generating a protector part for not
The computer backup method according to claim 7.

Images