Device and method for managing recovery information of auxiliary storage devices

Abstract

The present invention relates to an apparatus and method for efficiently managing the capacity of a backup auxiliary storage device within an auxiliary storage device. The auxiliary storage device 20 includes an original auxiliary storage device 30, a backup auxiliary storage device 40, and a user input device 50. The original auxiliary storage device 30, the backup auxiliary storage device 40, and the user input device 50 are controlled by a control device 60. The backup auxiliary storage device 40 stores recovery information for the original auxiliary storage device 30. The user input device 50 receives a user input for switching between a normal mode and a backup mode. In the normal mode, the control device 60 controls the auxiliary storage device 20 so that the host computer 10 boots using the OS of the original auxiliary storage device 30 and prevents access to the backup auxiliary storage device 40. In the backup mode, the control device 60 controls the auxiliary storage device 20 so that the host computer 10 boots using a copy of the OS stored in the backup auxiliary storage device 40 or an OS separately provided by the auxiliary storage device 20, and performs recovery of the original auxiliary storage device 30 based on the recovery information recorded by the backup auxiliary storage device 40.

Description

Technical Field

[0001] The present invention relates to an auxiliary storage device of a computer system, and more specifically, to an apparatus and method for managing recovery information of the auxiliary storage device.

Background Art

[0002] Recently, malicious codes such as ransomware not only encrypt user files but also sometimes delete partitions and folders containing system recovery information. Thus, when the entire system is controlled by one OS like in existing computer architectures, if malicious codes such as hacking programs and computer viruses gain control of the system with the highest administrator's credentials, it becomes impossible to prevent the system from being modified. Also, it is impossible to respond when a malicious third party temporarily obtains access rights and harms the system.

[0003] To address these issues, the applicant has filed several invention applications (Korean Patent Application Nos. 10-2017-0057998, Korean Patents 10-1920866 and 10-1920867). These prior applications deal with auxiliary storage devices, including original auxiliary storage devices and backup auxiliary storage devices. The original auxiliary storage device is always accessible to the host computer, while the backup auxiliary storage device is restricted to user access only under specific conditions (e.g., recovery mode conditions). Therefore, secure backup and recovery are possible using these prior applications. However, if backup information is recorded every time the host computer accesses the auxiliary storage device, a very large-capacity backup auxiliary storage device would be required. In particular, operating systems and application programs frequently create temporary files, but there is no need to create and save backup information for these temporary files. Consequently, if there is storage space that the user deems unnecessary to back up, this storage space also does not need to be backed up. Although the aforementioned prior application invention does not address this issue, it is extremely important in auxiliary storage devices to which the technology of the prior application invention is applied or similarly. In particular, when using SSDs (Solid State Drives) as auxiliary storage devices, such as in laptop computers, or in the case of high-capacity auxiliary storage devices in large-capacity servers, there is a large price difference depending on the capacity. Therefore, if a technology is provided that can efficiently manage the storage space of backup auxiliary storage devices, costs could be reduced significantly. [Overview of the project] [Problems that the invention aims to solve]

[0004] The present invention aims to propose a device that can efficiently manage the capacity of backup auxiliary storage devices within an auxiliary storage device by analyzing whether a backup exists or by deleting backed-up recovery information, thereby complementing the shortcomings of the recovery structure of a computer auxiliary storage device designed to include a backup auxiliary storage device in the aforementioned prior registered invention or a similar manner. [Means for solving the problem]

[0005] Thus, if the auxiliary storage device of the prior-filed invention is given a function to selectively create and save backup information, it would be possible to reduce the capacity of the backup auxiliary storage device, which would be a significant advantage in terms of cost. However, selectively creating backup information requires analysis of the access information transmitted when the host computer accesses the auxiliary storage device. For example, if the OS is in the process of deleting a temporary file and creating a new one, the information related to this would not need to be backed up. However, neither existing auxiliary storage devices nor the auxiliary storage device of the prior-filed invention embody any function that can determine this. A closer examination of this is as follows.

[0006] Generally, auxiliary storage devices perform operations such as reading and writing using proximity information transmitted from the host computer. In this process, the host computer primarily accesses the data area by specifying its address using the CHS (Cylinder Head Sector) addressing scheme or LBA (Logical Block Addressing) scheme, rather than using file names or folder names.

[0007] In other words, regardless of the method, addresses that directly or indirectly specify a particular area of ​​the storage space, such as the cluster number, head number, or sector number, are used because the host computer's file system is managed by the host computer, not the auxiliary storage device. Of course, some auxiliary storage devices can also exchange file-level information using separate protocols, but generally, products such as HDDs and SSDs widely used in desktop and laptop computers access auxiliary storage devices by directly providing addresses.

[0008] However, the access information transmitted at this time generally does not contain information such as file names or file paths. Therefore, in order to check whether or not there has been access to file system objects such as files, directories, or MBR (Master Boot Record), the access information must be analyzed from the auxiliary storage device. However, this work is unnecessary with typical existing auxiliary storage devices, and if such work were to be performed, it would only slow down the processing speed of the auxiliary storage device without any benefit.

[0009] In contrast, the auxiliary storage device according to the present invention, although slightly slower in processing speed due to performing such tasks, can manage the storage space for recovery information very efficiently, thereby significantly reducing manufacturing costs and providing users with a means to back up only the files and directories they desire. Moreover, since time-consuming tasks can be processed in the background, a decrease in processing speed can be prevented, making it even more efficient.

[0010] To solve the aforementioned problems, the first aspect of the present invention, which was completed by embodying the above concepts, is configured such that a host computer accesses (approaches) the auxiliary storage device, and the auxiliary storage device includes: an original auxiliary storage device; a backup auxiliary storage device that stores recovery information of the original auxiliary storage device; a user input device that receives user input for switching between normal mode and backup mode; and a control device that is connected to the original auxiliary storage device, the backup auxiliary storage device, and the user input device to control the normal mode and backup mode of the auxiliary storage device and manage the recovery information by user commands.

[0011] The auxiliary storage device controlled by the control device operates in normal mode and backup mode. This normal mode and backup mode can be selected by the user via the user input device. In normal mode, the control device controls the auxiliary storage device so that the host computer boots using the OS of the original auxiliary storage device and cannot access the backup auxiliary storage device. In backup mode, the control device controls the auxiliary storage device so that the host computer boots with a copy of the OS stored in the backup auxiliary storage device or with an OS provided separately by the auxiliary storage device, and performs recovery of the original auxiliary storage device based on the recovery information recorded in the backup auxiliary storage device.

[0012] The control device can be implemented with software and related hardware that handles the functional calculations of the CPU controlling the auxiliary storage device, but it can also be connected in various forms to the original auxiliary storage device, the backup auxiliary storage device, and the user input device, as in the prior art, and the user input device can be implemented as an electrical switch operated by the user. On the other hand, the user input device may be implemented in a manner that verifies one or more user inputs based on information transmitted by wire and wireless means using a communication module.

[0013] In one embodiment of the invention, the control device includes a recovery information management module that manages whether to create and save recovery information for the original auxiliary storage device.

[0014] Here, the recovery information management module may include: an access information analysis unit that analyzes access information provided by the host computer to access the original auxiliary storage device; a file system object confirmation unit that confirms a file system object currently using the storage space of the access address included in the access information; and a recovery information recording unit that, if the confirmed file system object is a recovery-needed object specified by the user, creates and records recovery information for the storage space of the access address.

[0015] On the other hand, in other embodiments, the recovery information management module may include: an access information analysis unit that analyzes access information provided by the host computer to access the original auxiliary storage device; a file system object verification unit that analyzes the host computer's file system and compares the storage space of the access addresses included in the access information with a search table created in a table to confirm file system objects that are using that space by comparing it with the sector and cluster information assigned to files and directories; and a recovery information recording unit that, if the confirmed file system object is a recovery-needed object specified by the user, creates and records recovery information for the storage space of the access addresses.

[0016] In another embodiment of the invention, the control device may include a recovery information deletion module that deletes recovery information from a previously stored original auxiliary storage device.

[0017] This recovery information deletion module may include: a recovery information analysis unit that extracts access addresses of recovery information previously stored in a backup auxiliary storage device; a file system object verification unit that identifies file system objects that use the access addresses included in the recovery information; and a recovery information deletion unit that deletes previously stored recovery information if the identified file system object is an object that does not require recovery as specified by the user.

[0018] The auxiliary storage device according to the second aspect of the present invention for solving the aforementioned problems further includes a display device in addition to the auxiliary storage device according to the first aspect. Here, the display device may consist of an LED, a display, an alarm device, etc., and according to other embodiments, it can be implemented in a manner similar to a user input device, consisting of a communication module, and confirming user input based on information transmitted by wire and wireless. Alternatively, the user input device and the display device may be integrated and configured as a single input / output device.

[0019] The control device for the auxiliary storage device relating to this second aspect may further include a user instruction input module that receives user instructions from a user input device; a display device drive module that drives a display device; and a recovery information maintenance module that deletes or compresses recovery information based on the input user instructions.

[0020] The recovery information preparation module may include: a recovery information analysis unit that analyzes recovery information previously stored in a backup auxiliary storage device to extract access addresses; a file system object confirmation unit that checks which file system objects are currently using the storage space for the access addresses; and a recovery information deletion unit that determines whether the confirmed file system object is a file system object designated for deletion in a user command, and deletes the recovery information if they match.

[0021] On the other hand, the recovery information preparation module may, in other embodiments, include: a recovery information analysis unit that analyzes recovery information previously stored in a backup auxiliary storage device to extract access addresses; a file system object confirmation unit that identifies file system objects currently using the storage space for the access addresses; and a recovery information compression unit that determines whether the identified file system object is a file system object designated as a compression target in a user command, and compresses the recovery information if they match.

[0022] Here, the recovery information preparation module of the two embodiments may include a user instruction analysis unit that analyzes user instructions, and a preparation algorithm execution unit that performs functions such as deleting, compressing, and transmitting recovery information previously stored in the backup auxiliary storage device using a pre-configured algorithm corresponding to the analyzed user instructions. Furthermore, the recovery information preparation module of the two embodiments may further include an information display unit that displays information on the display means for the purpose of providing information generated in the process of performing the above-mentioned tasks or for additional user input.

[0023] According to yet another aspect of the present invention, there is provided a recovery information management method for executing or embodying the recovery information management apparatus of the auxiliary storage device described above by means of a method.

[0024] According to yet another aspect of the present invention, there are provided application devices such as a computer (PC), a server computer, a mobile phone, an automatic control device, etc. to which the recovery information management apparatus and / or the recovery information management method of the auxiliary storage device described above are applied.

[0025] The comprehensive configuration of the present invention introduced above will become clearer through the specific embodiments described later together with the drawings.

Effects of the Invention

[0026] The auxiliary storage device including the original auxiliary storage device and the backup auxiliary storage device according to the present invention manages recovery information and effectively utilizes the capacity of the backup auxiliary storage device, thereby significantly reducing the storage area required for backup and significantly reducing the production cost compared to products to which the technology according to the present invention is not applied. For example, in the case of a notebook computer or a tablet computer, due to its portability, even if the price is high to reduce the weight, an SSD (Solid State Drive) is mainly used as the auxiliary storage device, and a large-capacity server uses a very large-capacity auxiliary storage device. However, if the technology according to the present invention is applied, it is possible to install an auxiliary storage device that can recover data damaged by malicious software without incurring high costs, which is meaningful both commercially and socially.

[0027] More specifically, the auxiliary storage device according to the present invention can manage the storage space for recovery information very efficiently, so that the manufacturing cost can be significantly reduced, and there is an advantage that it is possible to provide a means for the user to back up only the files and directories that the user desires. Moreover, if operations that take a long time are processed as background operations, it is also possible to prevent a decrease in processing speed, so it is judged to be more efficient.

Brief Description of the Drawings

[0028] [Figure 1] It is a schematic diagram of an auxiliary storage device 20 according to an embodiment of the present invention. [Figure 2] It is a configuration diagram of a control device 60 of the auxiliary storage device 20 in FIG. 1. [Figure 3] It is a configuration diagram of an embodiment of a recovery information management module 620 of the control device 60 shown in FIG. 2. [Figure 4] It is a configuration diagram of a recovery information management module 620' according to another embodiment of the recovery information management module 620 of the control device 60 shown in FIG. 2. [Figure 5] It is a configuration diagram of a recovery information deletion module 630 of the control device 60 shown in FIG. 2. [Figure 6] It is a schematic diagram of an auxiliary storage device 20 according to another embodiment of the present invention. [Figure 7] It is a configuration diagram of a control device 60 of the auxiliary storage device 20 in FIG. 6. [Figure 8] It is a configuration diagram of a recovery information maintenance module 650 in FIG. 7. [Figure 9] It is a configuration diagram of a recovery information maintenance module 650' according to another embodiment. [Figure 10] It is a component further included in the recovery information maintenance modules 650 and 650'.

Mode for Carrying Out the Invention

[0029] The advantages, features, and the method for achieving them of the present invention will become clear by referring to the embodiments described in detail together with the attached drawings. However, the present invention is not limited to the embodiments disclosed below and can be embodied in various different forms. However, this embodiment is provided to make the disclosure of the present invention complete and to fully inform those with ordinary knowledge in the technical field to which the present invention belongs of the scope of the invention. The technical scope of the present invention is defined by the claims.

[0030] On the other hand, the terms used herein are for illustrative purposes only and are not intended to limit the invention. In this specification, singular terms include plural terms unless otherwise specified in the text. The terms “comprises” or “comprising” used in this specification do not exclude the presence or addition of one or more other components, stages, operations and / or elements other than those mentioned.

[0031] Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings. In assigning reference numerals to the components in each drawing, the same reference numerals will be used for the same components as much as possible, even if they are shown in other drawings. Furthermore, in the description of the present invention, detailed descriptions of related known configurations or functions will be omitted if such descriptions would obscure the gist of the present invention.

[0032] Figure 1 is a schematic diagram of an auxiliary storage device 20 according to one embodiment of the present invention. Basically, the host computer 10 accesses (approaches) the auxiliary storage device 20.

[0033] The auxiliary storage device 20 includes an original auxiliary storage device 30 and a backup auxiliary storage device 40. In addition to the original auxiliary storage device 30 and the backup auxiliary storage device 40, there is also a user input device 50. These original auxiliary storage device 30, backup auxiliary storage device 40, and user input device 50 are controlled by a control device 60.

[0034] The backup auxiliary storage device 40 stores the recovery information from the original auxiliary storage device 30.

[0035] The user input device 50 is a device that receives user commands, and is used, for example, to input user commands to switch between normal mode and backup mode, or to input commands to the control device for preparing recovery information. The user input device 50 may be composed of an electrical switch, such as a mode selection switch, or it may be implemented as a communication module that confirms user input based on information transmitted via wired and wireless means. In this case, it is more preferable to use an encrypted communication protocol to enhance security.

[0036] The control device 60 is usually implemented with software and related hardware that handles the CPU's functional calculations for controlling the auxiliary storage device 20. However, for high-speed processing, it is also a good idea to implement the part that manages the access path to the original auxiliary storage device using hardware that utilizes an FPGA (Field Programmable Gate Array). When the mode selected by the user via the user input device 50 is the normal mode, the control device 60 controls the auxiliary storage device 20 so that the host computer 10 boots using the OS of the original auxiliary storage device 30 and cannot access the backup auxiliary storage device 40. Then, when the user selects the backup mode via the user input device 50, the control device 60 controls the auxiliary storage device 20 so that the host computer 10 boots with a copy of the OS stored in the backup auxiliary storage device 40 or with an OS separately provided by the auxiliary storage device 20, and performs tasks related to the recovery of the original auxiliary storage device 30 based on the recovery information recorded by the backup auxiliary storage device 40.

[0037] This configuration is fundamentally different in structure and function from commercially available auxiliary storage devices. However, the auxiliary storage device 20 having the above configuration has the advantage that even if the host computer 10 destroys the original auxiliary storage device 30 due to the intrusion of a malicious program, it can always be restored using the backup information stored in the physically completely isolated backup auxiliary storage device 40. In addition to this advantage, the present invention presents a configuration that can selectively manage backup information and efficiently reduce the amount of backup information.

[0038] The original auxiliary storage device 30 and backup auxiliary storage device 40 in Figure 1 can use general commercial HDDs or SSDs, or they may be directly implemented with non-volatile memory. The control device 60 is configured as shown in Figures 2 and 6.

[0039] Figure 2 is a diagram showing the configuration of the control device 60 of the auxiliary storage device 20 in Figure 1.

[0040] The control unit 60 includes a user command input module 610 that receives commands from a user input device 50, a recovery information management module 620 that manages recovery information of the backup auxiliary storage device 40, and a recovery information deletion module 630 that deletes the saved recovery information. While these modules are easily implemented in software within the control unit 60, it is preferable to implement some of them in hardware, as this can increase processing speed.

[0041] Figure 3 is a configuration diagram of one embodiment of the recovery information management module 620 within the control device 60 shown in Figure 2.

[0042] The recovery information management module 620 in the embodiment shown in Figure 3 consists of: an access information analysis unit 622 that analyzes access information provided by the host computer 10 to access the original auxiliary storage device 30; a file system object confirmation unit 624 that confirms a file system object currently using the storage space of the access address included in the access information; and a recovery information recording unit 626 that, if the confirmed file system object is a recovery-needed object specified by the user, creates and records recovery information for the storage space of the access address. While each of these units can easily be created as a software module and executed by the control device 60, high-speed processing is possible if they are implemented in hardware, similar to the lifespan management method for NVM (Non-Volatile Memory) such as flash memory.

[0043] In this case, if the access is for data storage, the access information may consist of the access time, the access address displayed using methods such as CHS or LBA, the type of host operation command such as write and read, and, in the case of a write operation, the data to be written. This information may be transmitted sequentially by the protocol used for communication between the host computer 10 and the auxiliary storage device, or it may be transmitted all at once in the form of block data. Furthermore, the recovery information may consist of the access time, access address, type of operation command, and data previously stored in the storage space specified by the access address, as included in the access information.

[0044] For example, suppose a command is issued from a host computer with an NTFS file system to write new data DATA_NEW to sector A, where existing information DATA_OLD is stored, to an auxiliary storage device. An existing commercial auxiliary storage device without a backup function would immediately write DATA_NEW to sector A without any steps to transfer or manage the existing information in sector A. As a result, DATA_OLD would be deleted and recovery would be impossible. However, the auxiliary storage device of the present invention, which has a backup function, will create recovery information for sector A and selectively save it to the backup auxiliary storage device 40 if sector A is the space used by an object that needs to be recovered.

[0045] On the other hand, recovery information for sector A can be created as follows and saved to the backup auxiliary storage device 40. Since this recovery information is inaccessible to the host computer 10 in normal mode, malicious software cannot delete it.

[0046] <Example of recovery information structure 1>

[0047] - Access time: 2018-12-31 17:00:00

[0048] -Physical address: Sector A

[0049] -Stored data:re_OLD

[0050] Here, the stored data may be named DATA_NEW depending on the storage method, but in this embodiment, let's assume that it stores existing information stored in the existing sector A. Recovery information is created in this manner and recorded in the backup auxiliary storage device 40, and from now on, DATA_NEW will be written to sector A of the original auxiliary storage device 30. Therefore, since DATA_OLD is stored, it can be recovered later.

[0051] On the other hand, in the auxiliary storage device according to the present invention, the recovery information management module 620 is responsible for structuring such recovery information. The recovery information management module 620 uses the access information analysis unit 622 to analyze whether the access is to access address sector A, and the file system object confirmation unit 624 confirms the file system object that is using the storage space of the access address to find the file system object that uses sector A.

[0052] Incidentally, a file system object basically refers to the elements or combinations of elements that make up a file system. Therefore, a file system object can be a sector, cluster, file path, file name, directory, partition, or drive itself, and these may be assembled together. Consequently, elements that make up the file system itself, such as the MBR (Master Boot Record), PBR (Partition Boot Record), and MFT (Master File Table) in the case of NTFS, and the FAT (File Allocation Table) in the case of a FAT file system, can also be file system objects. Therefore, a file system object may be a storage space such as a sector or cluster specified in CHS or LBA, may refer to a specific file such as c: / users / documents / korea.doc, may refer to a file in a directory meaning temporary use such as / temporary and the entire directory, may be a partition or drive such as drive D:, or may be a cluster such as MBR.

[0053] Therefore, the process of verifying the file system object using information such as "sector A" is a time-consuming process because it involves reverse tracking. However, if NTFS sector / cluster allocation information is created in advance as a search table, the time can be significantly reduced. Furthermore, it may be possible to reduce processing time by omitting this process in real time, creating general recovery information, recording it unconditionally, and then running a recovery information deletion module in the background. This will be explained in detail below. If file system object information is included, the recovery information can be structured as follows.

[0054] <Example of recovery information structure 2>

[0055] - Access time: 2018-12-31 17:00:00

[0056] - Physical address: Sector A, File system information: c: / User / Korea.doc

[0057] - Area information: 22334455......(512 bytes)

[0058] Subsequently, if the confirmed file system object is a recovery-required object specified by the user, the recovery information management module 620 will perform the step of creating recovery information for sector A as shown in the example of the recovery information configuration and recording the recovery information in the backup auxiliary storage device 40.

[0059] In other words, the auxiliary storage device according to the present invention has the advantage of significantly reducing the storage space of the backup auxiliary storage device 40 because it creates and stores only the recovery information of the recovery-needed objects that are designated as necessary for recovery (in contrast, the auxiliary storage device according to the prior art invention does not create or manage this information).

[0060] Designating which files need to be recovered and which do not can be done by providing the user with a means such as an initialization program. For example, a user can easily designate the boot partition (drive) C: as a file that does not need to be recovered and the user partition (drive) D: as a file that needs to be recovered. In such a case, since the system program and OS are included in the boot partition, the auxiliary storage device will only create and record recovery information for user files.

[0061] Further examination reveals the advantages of this invention even more clearly. For example, in the case of the Windows OS, the system file PAGEFILE.SYS is used as a kind of disk cache, and the OS accesses it as needed to temporarily store information. Also, application programs access the C: / Windows / Temp directory as needed to create files containing a lot of data, including log information. Furthermore, the Windows OS also creates and stores recovery information in the / System Volume Information directory whenever the system configuration changes, for its own recovery function.

[0062] However, files that are temporarily created or deleted while the OS is running do not need to be backed up. In the example above, if the file system objects using sector A are PAGAFILE.SYS and the files in / temp, then a backup is unnecessary. Also, the information in / System Volume Information is meaningless in the past and does not need to be recovered at all.

[0063] In this invention, sectors, clusters, files, directories, partitions, or drives that do not require recovery information management as described above can be designated and managed by the user as objects that do not need to be recovered. That is, if sector A itself belongs to objects that do not need to be recovered, or if sector A belongs to a file or directory that does not need to be recovered, when a write command to sector A is received from the host computer 10, the file system object verification unit 624 can immediately check whether it is an object that does not need to be recovered, and the procedure for creating recovery information can be omitted. Furthermore, it is also possible to implement this by creating and recording recovery information once, and then checking whether it is an object that does not need to be recovered using a background program and deleting the relevant information, thus enabling efficient management of the backup auxiliary storage device 40.

[0064] Figure 4 is a configuration diagram of a recovery information management module 620' relating to another embodiment of the recovery information management module 620 in the control device 60 shown in Figure 2. As mentioned above, this embodiment aims to reduce time by creating a search table in advance of NTFS sector / cluster allocation information in a way that allows for easy confirmation of file names and paths if the sector / cluster information is known.

[0065] The recovery information management module 620' in this embodiment consists of: a search table creation unit 621 that analyzes the file system of the host computer 10 and creates a table of sector and cluster information assigned to files and directories; an access information analysis unit 623 that analyzes access information provided by the host computer 10 to access the original auxiliary storage device; a file system object confirmation unit 625 that compares the storage space of the access addresses included in the access information with the search table to confirm file system objects currently in use; and a recovery information recording unit 627 that, if the confirmed file system object is a recovery-needed object specified by the user, creates and records recovery information for the storage space of the access addresses. In practice, the search table creation unit 621 may not have a creation function as it may only need to use a pre-created search table, but since the search table must always show the current state of the file system, it may also be responsible for the function of reflecting unreflected changes to the file system.

[0066] Here, the recovery information management module 620' is easily implemented in software and executed by the control unit, but if it is implemented in hardware, such as the management method for NVM (Non-Volatile Memory) like flash memory, high-speed processing is possible.

[0067] The search table creation unit 621 in this embodiment is necessary for file systems like Windows' NTFS. NTFS basically uses the MFT (Master File Table) to display various attributes of files and directories and their data locations. However, because the MFT displays information using the concept of entries, it is more difficult to intuitively confirm the location of files and directories compared to the FAT (File Allocation Table).

[0068] Therefore, in order to reduce the time required by the file system object verification unit 625, it is preferable to create a search table in the format of a File Allocation Table (FAT) or a method that analyzes the NTFS MFT (Master File Table) to easily confirm the file name and path if the sector / cluster information is known, thereby reducing the time required by the file system object verification unit 625. In this case, while the MFT manages the current status of cluster and sector occupation in a kind of concatenated data format, the search table manages the current status of cluster and sector occupation in a simple table, so object verification can be performed more quickly than when there is no search table.

[0069] However, the process of finding the actual disk space occupied by files and directories and creating a search table every time is time-consuming. Therefore, it is preferable to scan the entire storage area at boot time or system initialization and create and manage the search table all at once. Furthermore, the search table can be modified and managed each time a file or directory is newly created or deleted. This method is also necessary to reduce decision-making time in file systems such as HFS on Macs.

[0070] Figure 5 is a diagram showing the configuration of the recovery information deletion module 630 within the control device 60 shown in Figure 2. The recovery information deletion module 630 consists of a recovery information analysis unit 632 that extracts access addresses of recovery information previously stored in the backup auxiliary storage device 40; a file system object verification unit 634 that confirms file system objects that use the access addresses included in the recovery information; and a recovery information deletion unit 636 that deletes the previously stored recovery information if the confirmed file system object is an object that does not require recovery as specified by the user. At this time, the file system object verification unit 634 may use a search table during the object verification process.

[0071] The auxiliary storage device of the prior art invention basically creates and stores recovery information for all accesses that contain write commands from the host computer 10. However, the technology of the present invention can be applied by selectively deleting the stored recovery information after it has been verified through the object verification process according to the present invention. In this case, it is preferable that the recovery information deletion module 630 is executed as a background operation. For example, let's assume that the recovery information deletion module 630 is executed as a background operation. The recovery information deletion module 630 sequentially checks the recovery information, extracts the access address, compares it with the search table to check whether it is an object that does not need to be recovered, and if it is an object that does not need to be recovered, it is deleted, thereby preventing the waste of storage space in the backup auxiliary storage device 40.

[0072] Figure 6 is a schematic diagram of an auxiliary storage device 20 according to another embodiment of the present invention. It shows an embodiment in which a display device 70 is provided in addition to the auxiliary storage device 20 of Figure 1.

[0073] Here, the display device 70 is generally composed of LEDs, a display, an alarm device, etc., but it may also be implemented in a manner similar to the user input device 50, using a communication module to confirm user input based on information transmitted via wired and wireless means. Alternatively, the user input device 50 and the display device 70 may be integrated into a single input / output device.

[0074] Figure 7 is a configuration diagram of the control device 60 of the auxiliary storage device 20 shown in Figure 6. It includes a user command input module 610, a display device drive module 640 that drives the display device 70, and a recovery information preparation module 650 that deletes or compresses recovery information based on input user commands. The recovery information preparation module 650 will be described below.

[0075] Figure 8 is a configuration diagram of one embodiment of the recovery information preparation module 650 shown in Figure 7. This recovery information preparation module 1650 consists of a recovery information analysis unit 652 that analyzes recovery information previously stored in the backup auxiliary storage device 40 and extracts access addresses; a file system object confirmation unit 654 that checks the file system object currently using the storage space of the access addresses; and a recovery information deletion unit 656 that determines whether the confirmed file system object is a file system object designated for deletion in a user command, and deletes the recovery information if they match. At this time, the file system object confirmation unit 654 may use a search table during the object confirmation operation.

[0076] Figure 9 is a configuration diagram of another embodiment of the recovery information preparation module 650 of Figure 7. This recovery information preparation module 2650' consists of a recovery information analysis unit 651 that analyzes recovery information previously stored in the backup auxiliary storage device 30 and extracts access addresses; a file system object confirmation unit 653 that checks for file system objects currently using the storage space of the access addresses; and a recovery information compression unit 655 that determines whether the confirmed file system object is a file system object designated as a compression target in a user command, and compresses the recovery information if they match. At this time, the file system object confirmation unit 653 may use a search table during the object confirmation operation.

[0077] Figure 10 shows elements that may be further included in the recovery information preparation module 1 or 2 (650, 650') of Figures 8 and 9. In addition to the components of the recovery information preparation module 1 or 2 (650, 650'), a user instruction analysis unit 657 that analyzes user instructions; and a preparation algorithm execution unit 658 that deletes or compresses recovery information pre-stored in the backup auxiliary storage device using a pre-stored algorithm specified by the analyzed user instructions. Furthermore, when the recovery information preparation module 1 or 2 (650, 650') is configured in this way, an information display unit 659 that displays information on the display device 70 of Figure 6 for the purpose of providing information generated in the process of selectively performing the above-mentioned tasks or for additional user input may be further included.

[0078] On the other hand, the aforementioned recovery information management modules 620, 620', the recovery information deletion module 630, the recovery information maintenance modules 650, 650', and the maintenance algorithm execution unit 658 can be manufactured on separate hardware or a single chip. Furthermore, some functions of these modules, such as the function of checking file system objects through a search table (625), can be separated and manufactured on separate hardware or a single chip. The integrated recovery information management chip has its own memory, CPU interface circuit, and high-speed arithmetic circuit, and can be implemented in a form that executes program code that embodies recovery information management functions, recovery information deletion functions, recovery information maintenance functions, or maintenance algorithm execution functions. In particular, processing information compression and decompression in hardware offers a significant advantage because it allows for high-speed processing.

[0079] On the other hand, the function (625) for verifying file system objects through a search table can be separated and implemented as a dedicated search chip using an FPGA (Field Programmable Gate Array) and a processing core. This dedicated search chip consists of a CPU interface circuit, a memory interface circuit that can independently access shared memory, dedicated memory, or the CPU's memory, and a processing core equipped with a search engine. It can then perform the task of verifying file system objects using sector and cluster information via the search table.

[0080] On the other hand, the present invention provides application devices such as computers (PCs), server computers, mobile phones, and automatic control devices to which the recovery information management device and / or recovery information management method for the auxiliary storage device of the present invention described above is applied.

[0081] Although the configuration of the present invention has been described in detail above through preferred embodiments, a person with ordinary skill in the art to which the present invention pertains will understand that the present invention may be implemented in specific forms different from those disclosed herein without altering its technical idea or essential features. The embodiments described above should be understood to be illustrative and not limiting in all respects. The scope of protection of the present invention is defined by the claims set forth below rather than by the above detailed description, and all modifications or alterations derived from the claims and the concept of equivalents should be interpreted as being within the technical scope of the present invention.

Claims

1. In the auxiliary storage device accessed by the host computer, Original auxiliary storage device; Backup storage device that stores recovery information from the original storage device; A user input device that receives user input to switch between normal mode and backup mode; and The control device is connected to the original auxiliary storage device, the backup auxiliary storage device, and the user input device, and controls the normal mode and backup mode of the auxiliary storage device and manages recovery information by user commands. The control device, when in normal mode, controls the auxiliary storage device so that the host computer boots using the OS of the original auxiliary storage device and access to the backup auxiliary storage device is impossible; when in backup mode, controls the auxiliary storage device so that the host computer boots with a copy of the OS stored in the backup auxiliary storage device or an OS provided separately by the auxiliary storage device; and performs recovery of the original auxiliary storage device based on the recovery information recorded in the backup auxiliary storage device. The control device is Includes a recovery information management module that manages whether to create and save recovery information for the original auxiliary storage device, The aforementioned recovery information management module is: An access information analysis unit analyzes the access information provided by the host computer to access the original auxiliary storage device, A file system object verification unit that verifies the storage space of the access address included in the aforementioned access information and the file system object currently using that space, The system includes a recovery information recording unit that, if the confirmed file system object is a recovery-needed object specified by the user, creates and records recovery information for the storage space of the access address, The control device is Includes a recovery information deletion module that deletes the recovery information of the original auxiliary storage device that has been saved in advance, The aforementioned recovery information deletion module is: A recovery information analysis unit extracts the access address of recovery information previously stored in the backup auxiliary storage device, A file system object verification unit analyzes the access addresses included in the recovery information and identifies the file system object that uses the corresponding access address. A recovery information management device for an auxiliary storage device, including a recovery information deletion unit that deletes pre-stored recovery information when the confirmed file system object is an object that does not require recovery as specified by the user.

2. The recovery information management device for an auxiliary storage device according to claim 1, wherein the file system object verification unit verifies a file system object that is using the storage space of the access address included in the access information by analyzing the file system of the host computer and comparing it with a search table created in a table that contains sector and cluster information assigned to files and directories.

3. The device further includes a display device that displays the results of the control operation of the control device, The control device A user instruction input module that receives user instructions from a user input device; A display device drive module for driving the aforementioned display device; and A recovery information management device for an auxiliary storage device according to claim 1, comprising a recovery information maintenance module that deletes or compresses recovery information based on input user commands.

4. The aforementioned recovery information preparation module is A recovery information analysis unit that analyzes recovery information previously stored in the aforementioned backup auxiliary storage device and extracts access addresses; A file system object verification unit that verifies the file system object currently using the storage space for the aforementioned access address; and A recovery information management device for an auxiliary storage device according to claim 3, comprising a recovery information deletion unit that determines whether the confirmed file system object is a file system object designated for deletion in a user command, and deletes the recovery information if they match.

5. The aforementioned recovery information preparation module is A recovery information analysis unit that analyzes recovery information previously stored in the aforementioned backup auxiliary storage device and extracts access addresses; A file system object verification unit that verifies the file system object currently using the storage space for the aforementioned access address; and A recovery information management device for an auxiliary storage device according to claim 3, comprising a recovery information compression unit that determines whether the confirmed file system object is a file system object designated as a target for compression in a user command, and compresses the recovery information if they match.

6. The aforementioned recovery information preparation module is User instruction analysis unit that analyzes user instructions; and The recovery information management device for an auxiliary storage device according to claim 4 or 5, further comprising a maintenance algorithm execution unit that performs functions such as deleting, compressing, or transmitting recovery information pre-stored in a backup auxiliary storage device using a pre-stored algorithm specified by an analyzed user command.

7. A recovery information management method performed on an auxiliary storage device accessed by a host computer, which includes an original auxiliary storage device; a backup auxiliary storage device that stores recovery information of the original auxiliary storage device; and a user input device that receives user input for switching between normal mode and backup mode. In the aforementioned normal mode, the host computer is booted using the OS of the original auxiliary storage device, and access to the backup auxiliary storage device is made impossible. When in the aforementioned backup mode, the host computer is configured to boot with a copy of the OS stored in the backup auxiliary storage device or an OS provided separately by the auxiliary storage device, and the recovery of the original auxiliary storage device is performed based on the recovery information recorded by the backup auxiliary storage device. A recovery information management stage that manages whether to create and save recovery information for the original auxiliary storage device when the user input device switches to backup mode, This includes a recovery information deletion step, which deletes the recovery information of the original auxiliary storage device that has been saved in advance, The aforementioned recovery information management stage is: The access information analysis stage involves analyzing the access information provided by the host computer to access the original auxiliary storage device, A file system object verification step, which verifies the file system object currently using the storage space of the access address included in the aforementioned access information, If the confirmed file system object is an object requiring recovery as specified by the user, the recovery information recording step includes creating and recording recovery information for the storage space of the access address, The aforementioned recovery information deletion step is, The recovery information analysis stage involves extracting the access address of the recovery information previously stored in the backup auxiliary storage device, The file system object verification step involves comparing the access addresses included in the recovery information with a search table to identify the file system object that uses the corresponding access address, and A method for managing recovery information for an auxiliary storage device, comprising: a recovery information deletion step, which deletes pre-stored recovery information when the confirmed file system object is an object that does not require recovery as specified by the user.

8. The method for managing recovery information of an auxiliary storage device according to claim 7, wherein the file system object verification step involves verifying a file system object that is using the storage space of the access address included in the access information by analyzing the host computer's file system and comparing it with a search table created in a table that contains sector and cluster information assigned to files and directories.

9. The auxiliary storage device further includes a display device, The method for managing recovery information of the auxiliary storage device is User command input stage where user commands are received from a user input device; A device drive step for driving the aforementioned device; and A method for managing recovery information for an auxiliary storage device according to claim 7, further comprising a recovery information preparation step of deleting or compressing recovery information based on input user commands.

10. The aforementioned recovery information preparation stage is Recovery information analysis step: Analyzing recovery information previously stored in the aforementioned backup auxiliary storage device to extract access addresses; A file system object verification step that verifies the file system object currently using the storage space of the aforementioned access address; and A recovery information management method for an auxiliary storage device according to claim 9, comprising a recovery information deletion step of determining whether the confirmed file system object is a file system object designated for deletion in a user command, and deleting the recovery information if they match.

11. The aforementioned recovery information preparation stage is Recovery information analysis step: Analyzing recovery information previously stored in the aforementioned backup auxiliary storage device to extract access addresses; A file system object verification step that verifies the file system object currently using the storage space of the aforementioned access address; and A recovery information management method for an auxiliary storage device according to claim 9, comprising a recovery information compression step of determining whether the confirmed file system object is a file system object designated as a target for compression in a user instruction, and compressing the recovery information if they match.

12. The aforementioned recovery information preparation stage is User instruction analysis stage, which analyzes user instructions; and A method for managing recovery information for an auxiliary storage device according to claim 10 or 11, further comprising a maintenance algorithm execution step which performs functions such as deleting, compressing, or transmitting recovery information pre-stored in a backup auxiliary storage device using a pre-stored algorithm specified by an analyzed user command.

Images