JP2000035920A - Fault restoration method for system and storage medium storing program for fault restoration of system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily restore the fault of a system in a short time. SOLUTION: In the system provided with a first auxiliary storage device where an operating system is installed a second auxiliary storage device capable of reading stored information from a detachable auxiliary storage medium (floppy disk 100) usable as a drive for activation and the third auxiliary storage device of a capacity larger than the first auxiliary storage device, (a) while the operating system functions, the information stored and held in the first auxiliary storage device beforehand is backed up in the third auxiliary storage device together with the operating system. (b) When the operating system does not function, by using a program (restoration program 100b) stored and held in the auxiliary storage medium (floppy disk 100) beforehand, the system is activated and the information backed up in the third auxiliary storage device is restored in the first auxiliary storage device.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system failure recovery method and a storage medium storing a system failure recovery program, and more particularly to an operating system (hereinafter referred to as an OS) installed in a hard disk device or the like.
S) and a storage medium storing a system failure recovery program when the system is damaged.

[0002]

2. Description of the Related Art Conventionally, in the case of workstations and personal computers used by companies and individuals, in order to prepare for a crash of a hard disk drive, data in the hard disk drive is regularly copied to a magnetic tape for backup. Have been done. In particular, in recent years, not only mechanical failure of the hard disk drive but also data has often been destroyed by computer viruses due to the development of networks, and the importance of backup has been increasing day by day.

Here, a general computer system will be described. FIG. 15 is a block diagram showing a general computer system. As shown in FIG. 1, a computer 1 includes a CPU 1a and a floppy disk 1c.
, A main memory 1d and an extended memory 1e.
The extension memory 1e is provided to extend the storage capacity of the main memory 1d, and is used in a general personal computer. However, depending on the system, only the main memory 1d may be sufficient.

A SCSI board 2 and a magnetic tape device 3 for storing and holding backup data are connected to the computer 1 via a bus, and further a display 4, a keyboard 5, a hard disk device 6 on which an OS is installed, A CD-ROM drive 7 is connected.

Various products have been conventionally used as the magnetic tape device 3. For example, “DAT (DAT)
SS), "Ditto", "Travan", "8m
There are standards such as "m data cartridge".

[0006] "DAT (Digital Audio Tape)"
Refers to a system that digitizes audio and records and reproduces it on a magnetic tape, or a tape cassette therefor.
(Digital Data Storage) is a storage system standardized using the same technology as “DAT”.

[0007] "Travan" is a series name of a tape cartridge developed by 3M, and is compatible with a QIC mini cartridge. Currently, "Travan
TR-1 / 2/3/4 '' has been commercialized, and the capacity when uncompressed is `` 400Mbytes / 800Mbytes / 1.6Gbytes / 4Gbytes '' respectively.
It is.

[0008] "Ditto" means IOMEGA
It is a storage system manufactured by the company and conforms to the standard “QIC3020-MC”, so it is compatible with the above “Travan”. The “8 mm data cartridge” is a tape device using a storage medium having the same shape as an 8 mm video cassette.

Now, in such a system, the OS
If the hard disk device 6 becomes unusable due to the destruction of the
S had to be installed. This is because the conventional restore program is a program attached to the OS or a program operating on the OS.
For this reason, it was necessary to make the OS usable when executing the restoration.

An OS generally used in a personal computer (for example, Windows 95 (Wind)
ows 95)), it is not possible to overwrite the executable file in use. That is, it is not possible to overwrite the OS on which the restore program is running, and therefore, at the time of restoration, it is necessary to install Windows 95 only to execute the restore program. Therefore, the system immediately after the restoration includes two windows, Windows 95 used for the restoration process and Windows 95 restored from the backup data.
The set will be present on the hard disk drive.

[0011]

However, if the backup data is restored after the OS is reinstalled as described above, the operation becomes complicated, and there is a problem that it takes time to reconstruct the environment. .

[0012] Many of the OSs currently used are:
It is becoming larger and larger each day, and it takes a long time to install, and furthermore, a large capacity space is required on a hard disk device. Therefore, it is very inefficient to create an OS environment dedicated for restoration as described above. In particular, when a sufficient capacity cannot be secured in the hard disk device at the recovery destination, a separate hard disk device must be prepared, which tends to cause a problem in a small-scale system such as a notebook personal computer.

An object of the present invention is to solve such a problem, and an object of the present invention is to provide a system failure recovery method which can be implemented simply and in a short time, and a storage medium storing a system failure recovery program. And

[0014]

In order to achieve the above object, a system fault recovery method according to a first aspect of the present invention provides a first auxiliary storage device in which an operating system is installed, A second auxiliary storage device usable as a drive and capable of reading information stored from a removable auxiliary storage medium;
In the failure recovery method for a system including a third auxiliary storage device having a larger capacity than the first auxiliary storage device,
(A) While the operating system is functioning, information previously stored and held in the first auxiliary storage device is backed up in the third auxiliary storage device together with the operating system; When the operating system stops functioning, the system is started using the program stored in advance in the auxiliary storage medium, and the information backed up in the third auxiliary storage device is stored in the third auxiliary storage device. 1 is restored to the first auxiliary storage device.

According to a second aspect of the present invention, there is provided the system for restoring a fault in the first aspect, wherein the first auxiliary storage device is a hard disk device.

According to a third aspect of the present invention, in the system for restoring a fault in the first aspect, the second auxiliary storage device is a floppy disk drive, and the auxiliary storage medium is a floppy disk. .

According to a fourth aspect of the present invention, in the system for restoring a fault in the first aspect, the third auxiliary storage device is a magnetic tape device.

The storage medium storing the system failure recovery program according to claim 5 of the present invention can be used as a boot drive and a first auxiliary storage device in which an operating system is installed. Failure recovery of a system including a second auxiliary storage device capable of reading information stored from a possible auxiliary storage medium and a third auxiliary storage device having a larger capacity than the first auxiliary storage device (A) While the operating system is functioning, the information previously stored in the first auxiliary storage device is stored in the third auxiliary storage device for each of the operating systems. A program to back up to the device,
(B) When the operating system stops functioning, the system is started in place of the operating system, and information backed up in the third auxiliary storage device is restored in the first auxiliary storage device. And a program to execute.

Further, the storage medium storing the system failure recovery program according to claim 6 is the storage medium according to claim 5, wherein the first auxiliary storage device is a hard disk device.

The storage medium storing the system failure recovery program according to claim 7 is the storage medium according to claim 5, wherein the second auxiliary storage device is a floppy disk drive, and the auxiliary storage medium is a floppy disk drive. It is a disk.

Further, the storage medium storing the failure recovery program for a system according to claim 8 is the storage medium according to claim 5, wherein the third auxiliary storage device is a magnetic tape device.

According to a ninth aspect of the present invention, in the storage medium storing the system failure recovery program according to the ninth aspect, the backup program and the restore program are different from each other. It is stored and held in a storage medium.

According to a tenth aspect of the present invention, in the storage medium storing the system failure recovery program according to the ninth aspect, a program for activating the system is separated from the restore program to activate the system. Is stored and held in an auxiliary storage medium different from the storage and holding of the restore program.

With this configuration, in the system failure recovery method of the present invention, an OS is installed on a hard disk device in order to start and restore the system using a program in a removable auxiliary storage medium. The restoration can be started without performing. Therefore, the system can be restored simply and in a short time.

Similarly, the storage medium storing the failure recovery program for the system according to the present invention uses the program in the removable auxiliary storage medium to start and restore the system. Restore can be started without installing. Therefore, the system can be restored simply and in a short time.

[0026]

Next, an embodiment of the present invention will be described with reference to the drawings. Note that the computer system used in the present embodiment is the same as the above-described conventional technology, and therefore, FIG.

FIG. 1 is a block diagram showing one embodiment of the present invention. As shown in FIG. 1, the floppy disk 100 stores a backup program 100a and a restore program 100b.

The backup program 100a performs backup by storing information stored in the hard disk device 6 on a magnetic tape together with the OS. The restore program 100b stores information previously backed up on an auxiliary storage medium such as a magnetic tape (hereinafter referred to as “restore program 100b”).
Backup data) to the hard disk drive 6
And restore the system and data.

These two programs are configured independently of each other, and any one of the programs can be arbitrarily executed by an operation of an operator. That is, either backup or restore can be arbitrarily performed. Therefore, the data may be stored and stored in separate floppy disks.

Of course, the backup program 100
Regarding a, the program may be improved so as to be automatically executed at a predetermined date and time every month, or to be automatically executed every predetermined day of the week. In such a case, it is necessary to copy the backup program 100a from the floppy disk 100 to the hard disk device 6 and make it resident in the main memory 1d or the extended memory 1e.

Next, the backup program will be described. FIG. 2 is a flowchart showing the operation of the backup program. As shown in the figure, the backup program includes steps 1 to 5, and each step implements a boot check function, a tape check function, a tape read function, an I / O function, and a backup processing function. In addition, this backup program
The data is read out to the main memory 1d or the extended memory 1e by 1a and executed by the CPU 1a.

That is, in step 1, it is confirmed that the hard disk device 6 serving as the backup source is a boot drive, and the address of this boot drive is stored in the extended memory 1e (boot check function).

Next, in step 2, it is confirmed whether or not the magnetic tape device 3 is connected (tape check function). Next, in step 3, it is checked whether a magnetic tape is mounted on the magnetic tape device 3 and whether the magnetic tape is formatted (tape read function).

Next, in step 4, various displays are made on the display 4 to urge the operator to select and input setting parameters (I / O function). Finally, in step 5, backup processing is started (backup processing function).

Here, each of the above steps will be described in more detail. FIG. 3 is a flowchart describing steps 1 and 2 of FIG. 2 in detail. First, in step 101, the backup program recognizes system information of the boot drive.

Next, in step 102, the address of the boot drive as a backup source is saved in the extended memory 1e from the system information obtained in step 101.

Next, in step 201, a product code is read from firmware installed in the magnetic tape device 3 to check whether the magnetic tape device 3 is connected to the computer 1.

The product code is obtained by encoding the manufacturer and product name of the magnetic tape device 3, the standard of usable magnetic tape, and the like. Therefore, by reading this product code, it is possible to know the specifications of usable magnetic tapes and the like. In particular, here, whether or not the magnetic tape device 3 is connected to the computer 1 can be determined based on whether or not the product code has been read.

Next, in step 202, if the product code can be read, it can be determined that the magnetic tape device 3 is connected, and the process proceeds to step 301 in FIG. On the other hand, when it is determined that the magnetic tape device 3 is not connected, the operator is prompted to connect the magnetic tape device 3 by displaying the fact on the display 4 or the like.

FIG. 4 is a flowchart describing step 3 of FIG. 2 in detail. First, in step 301, the state of the magnetic tape device 3 is confirmed. That is, it is confirmed whether or not a magnetic tape is mounted on the magnetic tape device 3.

Next, if it is determined in step 302 that a magnetic tape is mounted, the process proceeds to step 304. On the other hand, if the magnetic tape is not mounted, the flow shifts to step 303, and the fact is displayed on the display 4.
To prompt the operator to mount the magnetic tape.

Next, in step 304, since the magnetic tape device 3 is already in the ready state, the magnetic tape is rewound once, and then the volume information written at the head of the magnetic tape is read (step 305). The information is stored in the extension memory 1e (step 306).

Next, in step 307, it is determined from the read volume information whether the magnetic tape has been formatted. That is, if the magnetic tape has been formatted, volume information has been written, and if it has not been formatted, no volume information has been written.

Therefore, if the volume information has not been written, it is determined that the formatting has not yet been performed, and that fact is displayed on the display 4 to urge the operator to manually format the magnetic tape.

FIG. 5 is a flowchart describing the details of step 4 in FIG. In step 401, a message to confirm whether to start backup is displayed on the display 4. The operator who sees this display performs key input using the keyboard 5 (step 402).

Next, in step 403, as a result of the key input, if the backup is to be started, the process proceeds to step 405, and if the backup is to be stopped, the process proceeds to step 404 to complete the backup.

Next, at step 405, the hard disk drive 6 connected to the computer 1 and the numbers assigned to the partitions in the hard disk drive 6 are displayed on the display 4. For example, in Windows 95, any one of 26 types from A to Z is attached.

Then, the operator who sees this display makes a key input using the keyboard 5 (step 406).
As a result of the key input, if a hard disk device or the like to be backed up is selected, the process proceeds to step 408, and if not selected, the process returns to step 401 to confirm again with the operator whether to start the backup (step 407).

Next, in step 408, the display unit 4 displays the standard of the usable magnetic tape based on the product code read in step 201.
The operator who sees this display confirms whether the displayed standard is the standard he wants to use, performs key input using the keyboard 5, and proceeds to step 411. on the other hand,
If it is not the standard to be used, the flow returns to step 405 by key input.

Next, at step 411, a message to confirm is displayed on the display 4 in order to make a final confirmation of the start of backup. The operator who sees this display performs key input using the keyboard 5 (step 412).
Next, in step 413, if the backup is to be started, the process proceeds to step 501 in FIG. 6, and if the final confirmation is rejected, the process returns to step 408.

FIG. 6 is a flowchart describing details of step 5 in FIG. First, in step 501, the magnetic tape is rewound to the beginning of the write start position. Then, the previously written volume information is skipped (step 502), and the magnetic head is positioned at the head of the data area.

Next, at step 503, information is read from the hard disk device 6 on a file basis. At this time, if no read error occurs, step 507 is executed.
If the read error has occurred, go to step 50
Go to 5.

Next, in step 507, since no read error has occurred, the file is pseudo-opened on the main memory 1d or the extended memory 1e (step 507), and a file header is created for the opened file. The file information is edited, for example, by combining the file header and the actual data, and then the file is closed (step 508) and written on the magnetic tape (step 509).

Next, if no write error occurs in step 510, the process returns to step 503, and the above steps are repeated until all files in the hard disk device 6 are backed up. If a write error has occurred, the process proceeds to step 511 to execute a write error process, and then proceeds to step 512.

On the other hand, in step 505, if a read error occurs when reading the file, it is determined whether the file is "EOF (End Of File)". As a result, if “EOF”, step 512
Move to. If it is not "EOF", it is determined that a read error has occurred, and the process proceeds to step 506 to execute a read error process.

Next, in step 512, since the backup of all the files in the hard disk device 6 has been completed, the backup processing is terminated. As a result, all information including the OS in the hard disk device 6 can be backed up to the magnetic tape.

Next, an operation for restoring the backup data to the hard disk device, that is, a restoration procedure will be described. FIG. 7 is a flowchart showing the operation of the restore program. As shown in the figure, the restore program comprises steps 6 to 11, and each step includes a system start-up function, a magnetic tape device detection function, a magnetic tape volume check function, a hard disk detection function, an I / O function, and a restore processing function. Realize. This restore program is read by the CPU 1a into the main memory 1d or the extended memory 1e, and
Executed by PU1a.

That is, in step 1, the system is started from the floppy disk 1c to format the restoration destination hard disk device 6 (system startup function).

Next, in step 2, it is confirmed whether or not the magnetic tape device 3 is connected (magnetic tape device detection function). Next, in step 3, it is confirmed whether the data stored in the magnetic tape is written by a predetermined backup program (magnetic tape volume check function).

Next, the address of the hard disk device 6 to be restored is detected (hard disk detecting function).
Next, the operator is prompted to select and input parameters (I / O function). Next, execution of the restore processing is started (restore processing function).

FIG. 8 is a flowchart describing step 6 of FIG. 7 in detail. First, in step 601, the floppy disk 1c is mounted on the floppy disk drive 1b at the same time when the power of the computer 1 is turned on.

Then, the floppy disk drive 1b can be used as a start-up drive. When the floppy disk 1c is mounted, the contents of the floppy disk 1c are stored in the main memory 1d before the hard disk device 6. Is read.

As a result, the system is started up by the function of the starting means in the restore program. Then
In step 602, the hard disk device 6 to be restored is formatted. Next, in step 603, the restore program is executed by an operation such as input of a command by the operator.

FIG. 9 is a flowchart describing step 7 of FIG. 7 in detail. Here, the SCSI board 2 includes a SCSI such as a magnetic tape device or a hard disk device.
It is assumed that up to six devices can be connected.
Therefore, by reading the product code from the SCSI device connected to the computer 1, it is checked whether the magnetic tape device 3 is connected. So SC
A variable “CNT” for counting the number of SI devices is set, and “0” is stored in “CNT” as an initial value (step 701).

Next, in step 702, a product code is read from each of the SCSI devices connected to the computer 1. That is, the product code is read from the firmware installed in each SCSI device, and the product code is analyzed to determine whether the magnetic tape device 3 is connected to the computer 1 or not. If the magnetic tape device 3 is found, the process proceeds to step 707, and if not, the process proceeds to step 704.

Next, in steps 704 and 705, "1" is added to "CNT", and steps 702 to 704 are repeated until this "CNT" exceeds "6". However, when it is finally determined that the magnetic tape device 3 is not connected, the fact is displayed on the display 4 in step 706 to prompt the operator to connect the magnetic tape device 3.

On the other hand, after detecting that the magnetic tape device 3 is connected in step 707, the state of the magnetic tape device 3 is confirmed. That is, it is confirmed whether or not a magnetic tape is mounted on the magnetic tape device 3.
If the magnetic tape has been mounted, step 801 in FIG.
The process proceeds to step 709, and if not, the process proceeds to step 709, and the operator is informed on the display 4 (steps 708, 709).

FIG. 10 is a flowchart detailing step 8 of FIG. In step 801,
The magnetic tape is once rewound to retrieve the volume information of the magnetic tape. Then, the volume information is read (step 802).

Next, in step 803, the volume information of the magnetic tape is analyzed to confirm whether the magnetic tape is a tape storing and holding backup data. If it is a tape storing the backup data, the process proceeds to step 805, and if not, the process proceeds to step 804 to display the fact on the display 4 to replace the magnetic tape with a correct magnetic tape. Next, in step 805, the volume information read earlier is stored in the extension memory 1e.

FIG. 11 is a flowchart describing step 9 in FIG. 7 in detail. Here, a drive that can start the system is detected. That is, the drive address and the number of hard disk devices and floppy disk drives on the system are detected. Therefore, the hard disk drive 6 connected to the system
A variable "CNT" for counting the number of floppy disks and a variable "FDCNT" for counting the number of floppy disk drives 1b are set.

First, in step 901, “CN
The initial value “0” is stored in “T” and “FDCNT”.
On the other hand, in order to confirm the addresses of the hard disk device 6 and the floppy disk drive 1b, the file "IO.SYS" in the floppy disk 1c is read, and the execution result is changed to the variable "DRV".
_LST ".

At this time, if the value is "7xh", it means that the floppy disk drive has been detected, and "D
The address of the floppy disk drive stored in RV_LST is stored in a variable “DRV_ADRS”, and the pointer of “DRV_LST” is incremented by “+1”. Further, since one floppy disk drive has been detected, the variable “FDC_CNT” is set to “+1”.
(Steps 905, 909 to 911).

On the other hand, in step 906, if the confirmed value is "9xh", it means that the hard disk drive has been detected, and similarly, the address stored and held in "DRV_LST" is stored in "DRV_ADRS" ( (Step 907) The pointer of “DRV_LST” is incremented by “+1” (Step 908).

The processing of steps 903 to 913 is
Addresses A to Z that can be assigned by the system as a loop
Repeat for a minute (26 loops). Therefore, when one loop is completed, “CNT” is incremented by “+1”, and then it is determined whether or not the value of “CNT” is equal to “26”. If equal, step 1 in FIG.
001.

FIG. 12 is a flowchart describing step 10 of FIG. 7 in detail. In step 1001, a message to that effect is displayed on the display 4 to confirm whether or not to start restoration. The operator who has seen this inputs a key using the keyboard 5 (step 100).
2) If restoration is to be started, step 1005
If not, the process proceeds to step 1004 to execute a restore end process (step 100).
3).

Next, at step 1005, a final confirmation is made on the display 4 as to whether or not to start restoration. The operator who has seen this inputs a key using the keyboard 5 (step 100).
6) If the restoration is to be started, the process proceeds to step 1101 in FIG.
01 (step 1007).

FIG. 13 is a flowchart describing step 11 of FIG. 7 in detail. In step 1101, the magnetic tape mounted on the magnetic tape device 3 detected in step 7 is rewound to the head of the write start position, and the previously written volume information is skipped (step 1102). Then, the magnetic head is positioned at the head of the data area.

Next, data is read from the magnetic tape in block units. If a read error has not occurred, the process proceeds to step 1107;
Go to 5.

Next, in step 1105, it is determined whether or not the read file is “EOF”.
If "F", the process proceeds to step 1112. "EOF"
If not, the flow shifts to step 1106 to perform read error processing, and then shifts to step 1112.

On the other hand, if the data can be correctly read from the magnetic tape in step 1107, the read data is pseudo-opened as a file on the extended memory 1e.
It is divided into a file information section and a data section. After editing the file header and data of the opened file, the file is closed (step 1108).
Write to the hard disk device 6 (step 110)
9).

Next, in step 1110, if no write error has occurred, the flow returns to step 1101, and all the files in the magnetic tape are transferred to the hard disk drive 6.
Repeat the above steps until the data is restored. on the other hand,
When a write error has occurred, a write error process is performed in step 1111, and the process returns to step 1101. Finally, in step 1112, the restore processing ends.

As described above, according to the present invention, the entire information of the hard disk device 6 can be backed up to a magnetic tape, and the backed up data can be restored to the hard disk device 6.

Next, another embodiment of the present invention will be described. In the present invention according to FIG. 1, the backup program 100a and the restore program 100b are stored and held in one floppy disk 100, but it is difficult to store both programs in a small-capacity floppy disk. There is. Further, the backup program 100a is used only when the hard disk device 6 is normal, and need not always be stored and held on the floppy disk.

FIG. 14 is a block diagram showing another embodiment of the present invention. As shown in the figure, the floppy disk 200 includes a system boot program 200a.
And a floppy disk exchange display program 200b. The floppy disk 300 stores a restore program 300a.

That is, when starting up the system, the floppy disk 20
0 is mounted on the floppy disk drive, and the system is started by the operation of the system start program 200a. After the system is started, the display 4 indicates that the floppy disk is to be replaced by the operation of the floppy disk replacement display program 200b.

Then, the operator who sees this display takes out the floppy disk 200 from the drive, and mounts the floppy disk 300 in the drive instead. As a result, by the operation of the restore program 300a,
Restore processing is started. Since the backup program is not used at the time of restoration, it may be provided on a floppy disk different from the above,
Floppy disks 200 and 300 if there is enough space
May be stored. Further, the restore program 300a may not include the function of starting the system.

In the above embodiment, the restore program and the like are stored and held in the floppy disk. However, other auxiliary storage media may be used as long as the system can be started. It is apparent that the present invention can be applied not only to backup of information in a hard disk device but also to backup of information in other storage media. Naturally, if the capacity of the magnetic tape is larger than that of the hard disk drive, all the backup data can be stored and held on one magnetic tape, and conversely, when the capacity of the magnetic tape is small. The backup data may be divided and stored in a plurality of magnetic tapes. Further, instead of the magnetic tape, a storage medium such as an optical disk or a magneto-optical disk may be used.

[0088]

As described above, the failure recovery program for the system according to the present invention can be detached without re-installing the OS in the first auxiliary storage device when reconstructing the computer system. It is possible to start up the system by using a program stored in a suitable auxiliary storage medium and restore information previously backed up in the third auxiliary storage device to the first auxiliary storage device.

Therefore, there is no need to install a dedicated OS for restoration or installation of a restore program as in the related art, and the OS and other application software can be simultaneously and easily restored. The time required for restoring can be greatly reduced.

Similarly, the medium storing the system failure recovery program according to the present invention does not require the OS to be re-installed in the first auxiliary storage device when the computer system is reconfigured. The system can be started using a program stored in a possible auxiliary storage medium, and information previously backed up in the third auxiliary storage device can be restored in the first auxiliary storage device.

Therefore, it is not necessary to install a dedicated OS for restoration or to install a restore program as in the related art, and the OS and other application software can be simultaneously and easily restored. The time required for restoring can be greatly reduced.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram showing one embodiment of the present invention.

FIG. 2 is a flowchart showing a backup program according to FIG. 1;

FIG. 3 is a flowchart showing steps 1 and 2 of FIG. 2;

FIG. 4 is a flowchart showing Step 3 of FIG. 2;

FIG. 5 is a flowchart showing Step 4 of FIG. 2;

FIG. 6 is a flowchart showing Step 5 of FIG. 2;

FIG. 7 is a flowchart showing a restore program according to FIG. 1;

FIG. 8 is a flowchart showing Step 6 of FIG. 7;

FIG. 9 is a flowchart showing Step 7 of FIG. 7;

FIG. 10 is a flowchart showing Step 8 of FIG. 7;

FIG. 11 is a flowchart showing Step 9 in FIG. 7;

FIG. 12 is a flowchart showing Step 10 of FIG. 7;

FIG. 13 is a flowchart showing Step 11 of FIG. 7;

FIG. 14 is an explanatory diagram showing another embodiment of the present invention.

FIG. 15 is a block diagram showing a general computer system.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Computer, 1a ... CPU, 1b ... Floppy disk drive, 1c, 100, 200, 300 ... Floppy disk, 1d ... Main memory, 1e ... Expansion memory, 2 ... SCSI board, 3 ... Magnetic tape device, 4 ... Display, 5: Keyboard, 6: Hard disk drive, 7: CD-ROM drive, 100a: Backup program, 100b, 300a: Restore program, 200a: System boot program, 200b: Floppy disk exchange display program

Claims (10)

[Claims] 1. A first auxiliary storage device in which an operating system is installed, and a second auxiliary storage device which can be used as a boot drive and can read information stored in a removable auxiliary storage medium. In a method for restoring a system including a device and a third auxiliary storage device having a capacity larger than that of the first auxiliary storage device, (a) while the operating system is functioning, the first The information stored in the auxiliary storage device is backed up in the third auxiliary storage device together with the operating system, and (b) when the operating system stops functioning, the information is stored and stored in the auxiliary storage medium in advance. Using the stored program, start the system and back up to the third auxiliary storage device Error recovery method of the system, characterized in that to restore the keep information in the first auxiliary storage device. 2. The method according to claim 1, wherein the first auxiliary storage device is a hard disk device. 3. The method according to claim 1, wherein the second auxiliary storage device is a floppy disk drive, and the auxiliary storage medium is a floppy disk. 4. The method according to claim 1, wherein the third auxiliary storage device is a magnetic tape device. 5. A first auxiliary storage device in which an operating system is installed, and a second auxiliary storage device which can be used as a boot drive and can read information stored in a removable auxiliary storage medium. In a storage medium storing a failure recovery program for a system including a device and a third auxiliary storage device having a larger capacity than the first auxiliary storage device, (a) while the operating system is functioning A program for backing up information previously stored in the first auxiliary storage device to the third auxiliary storage device for each of the operating systems; and (b) when the operating system stops functioning. Then, a system is started in place of the operating system, and the third supplement is started. The storage medium storing the system failure recovery program that is characterized in that a program for restoring data that has been backed up in the first auxiliary storage device in the storage device. 6. The storage medium according to claim 5, wherein the first auxiliary storage device is a hard disk device. 7. The storage device according to claim 5, wherein the second auxiliary storage device is a floppy disk drive, and the auxiliary storage medium is a floppy disk. Medium. 8. The storage medium according to claim 5, wherein the third auxiliary storage device is a magnetic tape device. 9. The system according to claim 5, wherein the backup program and the restore program are stored in different auxiliary storage media. Storage medium that stores. 10. The program according to claim 9, wherein a program for activating the system is separated from the restore program, and a program for activating the system is supplemented by a program different from the one in which the restore program is stored and held. A storage medium storing a failure recovery program for a system, wherein the storage medium is stored in a storage medium.