KR102084661B1 - Method and computer apparatus for disk managemt - Google Patents

Abstract

A disk management method and a computer device performing the same are provided. This method is a disk management method of a computer device, comprising: creating a base disk in which an operating system is stored and set to a user-specified state, and from a previously created incremental disk of all logical addresses representing the storage space of the base disk; Referring to an unused logical address, creating a new incremental disk for storing data according to the operation of the operating system, and managing the base disk and the plurality of incremental disks in a hierarchical structure in the order of creation, and incrementing Performing a backup or restore on a disk basis.

Description

Disk management method and computer device that performs it {METHOD AND COMPUTER APPARATUS FOR DISK MANAGEMT}

The present invention relates to a disk management method and a computer device for performing the same.

The storage space used by users continues to increase.

Traditional backup and recovery methods have been accomplished by writing data directly to designated disk space. At this time, the process of writing and erasing the actual data takes a long time physically.

Therefore, when an infection such as a virus or ransomware occurs on the disk, it is difficult to restore and takes a long time even to restore.

SUMMARY OF THE INVENTION An object of the present invention is to provide a disk management method for abstracting a disk space based disk and an incremental disk into a hierarchical structure, performing a backup or restore in incremental disk units, and a computer device performing the same.

According to one aspect of the invention, the disk management method is a disk management method of a computer device, the operating system is stored, creating a base disk set in a user-specified state, the overall display of the storage space of the base disk Referring to an unused logical address in a previously created incremental disk among the logical addresses, creating a new incremental disk for storing data according to the operation of the operating system, and creating the base disk and a plurality of incremental disks Managing a hierarchical structure in order, and performing backup or restore in incremental disk units.

The performing of the backup or restore may include removing at least one incremental disk consecutive from a selected layer among a plurality of layered incremental disks and performing restoration to an incremental disk corresponding to the selected layer. .

The performing of the restoring may include checking an incremental disk to determine whether a difference between an incremental disk size of the top layer and an incremental disk size one layer below the top layer is greater than or equal to a predetermined threshold value, and the threshold value is greater than or equal to the threshold value. In this case, the method may include removing the top-level incremental disk by determining that the virus or malware is infected.

The performing of the restoration may include checking at least one file of a predetermined format stored on an incremental disk, and the files of the predefined format are above a predetermined threshold or the file header format is not a registered format. In this case, the method may include determining that the ransomware is infected and removing the corresponding incremental disk.

The performing of the restoration may include determining that the virus is infected and removing the corresponding incremental disk if the file name and the file path stored in the incremental disk are a predefined special path.

The performing of the backup or restore may include selectively backing up the incremental disks from the highest layer to any previous layer according to the entire incremental disk or a policy among a plurality of incremental disks generated at each boot. .

The generating at boot may include creating a new incremental disk referring to an unused logical address of a previously created incremental disk among the entire logical addresses at boot time, and generating data from a logical address referenced by the new incremental disk. De-reference of the logical address used for storage, and allocating the disk space corresponding to the dereferenced logical address as storage space of the incremental disk independently of the base disk.

According to another aspect of the present invention, a disk management method is a disk management method of a diskless management server connected to a diskless terminal through a network, and when a boot request is received from the diskless terminal, the storage space of the base disk is determined. Generating an incremental disk referencing an unused logical address in a previously generated incremental disk among all displayed logical addresses, transmitting boot information including operating system information and incremental disk information to the diskless terminal, And performing booting according to the boot information, and storing data according to an operation of the operating system in the generated incremental disk.

The base disk and the plurality of incremental disks have a hierarchical structure in the order of creation, and before the step of generating the incremental disk, the step of checking the pre-created incremental disk, and the disk capacity of the pre-generated incremental disk At least one of the above-defined thresholds, files of a particular format are above a predefined capacity, at least one of a file header format is not a registered format, and a stored file name and file path are predefined special paths. If applicable, the method further includes removing an incremental disk of a corresponding layer or an incremental disk of at least one layer consecutive from the corresponding layer, wherein the generating comprises: incrementing the next layer of the removed layer. You can create a disk.

The base disk and the plurality of incremental disks have a hierarchical structure in the order of creation, and after the storing, inspecting the incremental disk, the result of the check, the file having a specific format if the disk capacity is greater than or equal to a predetermined threshold. Removing the checked incremental disk if the file header format is not a registered format, and if the stored file name and file path are at least one of the predefined special paths. It may further include.

According to another aspect of the invention, the computer device is a storage device including a physical disk, a base disk and at least one incremental disk, a program for managing the base disk and the at least one incremental disk in a hierarchical structure in the order of creation And a processor configured to execute the program in association with the storage device and the memory device, wherein the program executes booting using the base disk, before booting or after booting ends. Instructions for creating the incremental disk and performing backup or restore in incremental disk units, wherein the base disk is a logical address indicating a second disk space of the physical disk except for the first disk space. And wherein the plurality of incremental disks are Each logical address is referred to each of the entire logical addresses, and data according to the operation of the operating system is stored.

The program may be configured such that when the disk capacity is greater than or equal to a predetermined threshold among the plurality of incremental disks, when files of a specific format are greater than or equal to a predetermined capacity, the file header format is not a registered format, and the stored file name and file path are different. It may include instructions for performing restoration by removing an incremental disk of a layer corresponding to at least one of the cases of a predefined special path or an incremental disk of at least one layer consecutive from the corresponding layer.

The program may include instructions for selecting, from the plurality of incremental disks, the entire incremental disk or an incremental disk from the top layer to any previous layer as a backup target, and removing the remaining unselected incremental disks.

According to an embodiment of the present invention, the disk storage space is abstracted into a hierarchical structure of a base disk and an incremental disk, and backup and restore are performed in incremental disk units. Thus, by removing only the incremental disks on which a virus or malicious code infection has occurred, the backup or restore time is shortened as compared with the conventional one.

In addition, you can create and store incremental disks independently at every boot and sequentially remove tiered incremental disks, making it easy to restore to a previous state.

In addition, virus and ransomware scans are performed in incremental disk units, and only files that have changed can be saved, thereby reducing the time required for diagnosing a problem state.

1 is a diagram schematically illustrating a layered disk structure according to an embodiment of the present invention.
2 is a diagram illustrating incremental disc creation, according to one embodiment of the invention.
3 is a diagram illustrating an incremental disc creation according to another embodiment of the present invention.
4 is a flowchart illustrating a disk management method according to an embodiment of the present invention.
5 is a flowchart illustrating a disk management method according to another embodiment of the present invention.
6 is a flowchart illustrating a disk management method according to another embodiment of the present invention.
7 is a flowchart illustrating a disk management method according to another embodiment of the present invention.
8 is a flowchart illustrating a disk management method according to another embodiment of the present invention.
9 shows an incremental disc list, according to an embodiment of the invention.
10 is a block diagram of a diskless system according to an embodiment of the present invention.
11 is a flowchart illustrating a diskless operation method according to an embodiment of the present invention.
12 illustrates a boot screen according to an embodiment of the present invention.
13 is a hardware configuration diagram of a computer device for performing disk management according to an embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, except to exclude other components unless specifically stated otherwise.

In addition, the terms “… unit”, “… unit”, “module”, etc. described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware or software or a combination of hardware and software. have.

A disk management method and a computer device performing the same according to an embodiment of the present invention will now be described with reference to the drawings.

1 is a diagram schematically illustrating a layered disk structure according to an embodiment of the present invention.

Referring to FIG. 1, the disk space of a physical disk is abstracted into a hierarchical structure of a base disk and a plurality (n) of incremental disks.

Physical disk means actual disk space. Physical disks are divided into units such as partitions or blocks, and logical disks are composed of a set of divided units.

Partitioning a physical disk into several logical storage areas is called a partition. A file system sees a disk as a collection of logical disk blocks. At this time, the disk block is a logical number, that is, 0, 1, 2. Has a logical number such as Thus, a logical disk is at least one partition set or at least one disk block.

Logical disks are divided into base disks and incremental disks. The base disk is defined as an initial state in which an operating system (OS) is installed or an operating system (OS) and applications are installed and a version arbitrarily designated by a user.

Incremental disks are defined as disks that store data that has changed in the state of the underlying disk, that is, data.

Incremental disks are created independent of previously created incremental disks at boot time or at the end of booting and are based on the base disk. Incremental disks refer to some logical address of the logical address representing the storage space of the underlying disk to store data according to the operation of the operating system (OS). Here, the stored data includes programs, files.

The base disk and the plurality of n incremental disks have a hierarchical structure in the order of creation. For example, an n-layer incremental disk is created later than an n-1 layer incremental disk, and an n-layer incremental disk has priority over backup or restore over an n-1 layer incremental disk.

Here, the backup is made in incremental disk units. Restoration is then done by removing incremental disks from the top layer to any previous layer.

2 is a diagram illustrating incremental disc creation, according to one embodiment of the invention.

Referring to FIG. 2A, logical addresses 0 and a indicating a storage space of a base disk may be mapped to a physical address of a physical disk or may indicate a location of a physical disk.

The operating system (OS) is stored in the disk space indicated by the logical addresses (0, a) of the base disk. The remaining disk space of the base disk may be an initial state set to empty space or a state where programs designated by a user are stored.

2 (a) assumes the first booting. That is, the case of creating an incremental disk for the first time.

In this case, the incremental disk 1 may refer to some logical addresses a and b of the entire logical addresses 0 and b of the base disk except for the disk space in which the operating system OS is stored. It can be referred to as a set of disk blocks corresponding to some logical addresses (a, b).

When booted, incremental disk 1 is created. The data according to the operation of the operating system OS are stored in the incremental disk 1. Here, the disk space for storage may be allocated consecutive disk blocks or discontinuous disk blocks among the disk blocks corresponding to the logical addresses (a, b). In FIG. 2A, consecutive disk blocks, that is, disk blocks corresponding to logical addresses c and d, are used.

At this time, among the logical addresses a and b referred to by the incremental disk 1, the reference of the logical addresses c and d allocated to the storage space is released. The disk space corresponding to the dereferenced logical address is allocated to the storage space of the incremental disk independently of the underlying disk.

When the base disk and the incremental disk 1 overlap, the abstract disk as shown in FIG. 2 (b) is implemented, and the operating system OS uses or recognizes the abstract disk. That is, the operating system OS recognizes the abstract disk as shown in FIG. 2B, but the abstract disk is a hierarchical structure of the base disk and the incremental disk 1, and backup and restore are performed in incremental disk units.

3 is a diagram illustrating an incremental disk creation according to another embodiment of the present invention, and illustrates an incremental disk creation according to a reboot operation.

Referring to FIG. 3A, upon rebooting, incremental disk 2 is created. Incremental disk 2 refers to logical addresses (a, c) and (d, b) of the logical addresses (a, b) of the base disk except for the logical addresses (c, d) used by the incremental disk 1 previously created. do. At reboot or after the reboot is finished, data according to the operation of the operating system (OS) is stored on incremental disk2. At this time, discrete disk blocks are allocated for storage, and logical addresses (e, f) and (g, h) are used.

At this time, the logical addresses (e, f) and (g, h) allocated to the storage space among the logical addresses (a, c) and (d, b) referred to by the incremental disk 2 are released. The disk space corresponding to the dereferenced logical addresses (e, f), (g, h) is allocated to the storage space of the incremental disk independently of the underlying disk.

When the base disk and the incremental disks 1 and 2 overlap, the abstract disk as shown in (b) of FIG. 3 is implemented, and the operating system OS uses or recognizes the abstract disk.

Incremental disks created as shown in Figs. 2 and 3 are increased in capacity when a file change or file creation operation is performed in the operating system (OS). That is, the physical disk space allocated to incremental disks increases.

Incremental disks use a method of referencing the physical address of the underlying disk and releasing references during storage, thus saving storage space than the underlying disk.

A method of managing the abstract disk of the structure described so far will be described below by embodiment. In this case, the disk management method may be performed by an operating system (OS) or a separate disk management program.

4 is a flowchart illustrating a disk management method according to an embodiment of the present invention, and illustrates an operation of a cup computer device equipped with an operating system (OS).

Referring to FIG. 4, the computer device generates a base disk (S101). In addition, referring to an unused logical address of a previously created incremental disk among the entire logical addresses representing the storage space of the underlying disk, a new incremental disk is created for storing data according to the operation of the operating system (OS) ( S103). Here, the new incremental disk may be created before loading the operating system (OS) or after shutting down the operating system (OS).

The computer apparatus manages the base disk and the plurality of incremental disks in a hierarchical structure according to the generation order (S105), and performs backup or restore in incremental disk units (S107).

Here, the computer device backs up the data generated at the boot time or after the boot end in independent incremental disk units.

The computer device may remove the higher layer incremental disk to return the computer environment to its previous state.

When a computer device removes an incremental disk, it only removes the abstract disk connection, so that it can be quickly restored to its previous state.

After booting, the user can select from a plurality of previously created incremental disks to apply to the computer environment. The computer device then applies the stored data of the incremental disk selected by the user to the computer environment after booting.

The computer device may predefine and use incremental disk creation criteria and policies. Such incremental disk creation criteria and policies may be stored and executed in an operating system (OS) or a separate disk management program.

The computer device may be created before the operating system (OS) is loaded or at the stage in which the operating system (OS) is shut down. The computer device may create a policy in combination with time information, number of times, number of incremental disks.

According to one embodiment, the computer device may create an incremental disk only once after bootup, every day after 06:00. In other words, every day after 6 o'clock, an incremental disk can be created before the operating system (OS) is loaded.

According to another embodiment, the computer device may create an incremental disk each time on shutdown during the week, ie whenever the operating system (OS) shuts down.

According to another embodiment, the computer device creates an incremental disk every day after 6 o'clock, but before the operating system (OS) is loaded at boot time. At this time, the ten most recent incremental disks are maintained, and all previously created incremental disks can be deleted.

5 is a flowchart illustrating a disk management method according to another embodiment of the present invention, and illustrates an operation of a cup computer apparatus on which an operating system (OS) is mounted.

Referring to FIG. 5, the computer device checks the size of a plurality of layered incremental disks (S201). The difference between the incremental disk sizes, i.e., the threshold at which the highest (n) layer, that is, the most recently generated incremental disk size, and the incremental disk size of the previous (n-1) layer is compared (S203), is defined. It is determined whether or not it is abnormal (S205). Here, the incremental unit may be KB, MB, or GB.

If it is determined in step S205 that the difference between the incremental disk sizes is greater than or equal to the threshold value, it is determined that the virus infection or ransomware infection (S207). Then, the incremental disk of the layer n is removed (S209).

When infected with a virus or ransomware, a large number of files are modified. Therefore, the capacity of the corresponding incremental disk increases rapidly. Therefore, if the capacity of the incremental disk increases sharply, it is highly likely that the virus and ransomware have been infected, and thus, the infection of the virus and ransomware can be detected using this feature. And by removing only the incremental disks where infections were detected, you can easily restore your computer environment before infection.

6 is a flowchart illustrating a disk management method according to another embodiment of the present invention, and illustrates an operation of a cup computer apparatus on which an operating system (OS) is mounted.

Referring to FIG. 6, the computer device checks a file in incremental disk units (S301). At this time, files of a predefined format are extracted (S303).

According to one embodiment, the predefined format may be a document file. For example, if a large amount of document files (DOCS, XSLX, PPTX, etc.) are present on an incremental disk, it is most likely infected with ransomware.

Therefore, it is determined whether the number of files extracted in step S305 is greater than or equal to a predetermined threshold number (S305). If it is determined to be abnormal, it is determined as ransomware infection (S307). The corresponding incremental disk, that is, the incremental disk from which the file is extracted, is removed (S309) and restored to the previous infection.

7 is a flowchart illustrating a disk management method according to another embodiment of the present invention, and illustrates an operation of a cup computer device equipped with an operating system (OS).

Referring to FIG. 7, the computer device checks a file in incremental disk units (S401) and confirms a file header format (S403). At this time, only the header of the document file can be checked.

It is determined whether the checked file header format is a registered format (S405). If it is not a registered format, that is, a known format, it is determined as a ransomware infection (S407) and the corresponding incremental disk is removed (S409), thereby restoring to the previous infection.

8 is a flowchart illustrating a disk management method according to another embodiment of the present invention, and illustrates an operation of a cup computer device having an operating system (OS).

Referring to FIG. 8, the computer apparatus checks a file in incremental disk units (S501), and determines whether a file name and a file path exist in a special path, for example, WINDOWS, SYSTEM32, or the like (S503).

If it is determined in step S503 that the file and file path exist in a special path, it is determined as a virus infection (S505) and the corresponding incremental disk is removed (S507), thereby restoring to the previous infection.

9 shows an incremental disc list, according to an embodiment of the invention.

Referring to FIG. 9, an incremental disk list managed by an operating system (OS) or a disk management program of a computer device may include creation time (year, month, day, hour, minute, second) of an incremental disk, and incremental disk identification number ( 1. disk, 2. disk, 3. disk, 4. disk) and path. Here, the path may be a logical address of the incremental disk.

The above-described configuration may be implemented in a diskless system and will be described with reference to FIGS. 10, 11, and 12.

10 is a block diagram of a diskless system according to an embodiment of the present invention.

Referring to FIG. 10, a diskless system includes a plurality of diskless terminals 100, a diskless management server 200, and a physical disk 300. In this case, the plurality of diskless terminals 100 are connected to the diskless management server 200 through the network 400.

Here, the plurality of diskless terminals 100 are not provided with a storage device such as a hard disk (HDD) or a solid state drive (SSD), and include a network interface card and a network driver required for remote booting.

The plurality of diskless terminals 100 use virtual disks provided by the diskless management server 200 through the network 400.

The protocol used between the plurality of diskless terminals 100 and the diskless management server 200 may be selected from protocols capable of using a remote disk through a network 400 such as iSCSI (Internet Small Computer Systems Interface), NFS, and SMB. do. This protocol is a protocol for transmitting disk data over an IP-based network used in a PXE environment.

The diskless management server 200 remotely boots the diskless terminal 100, performs disk management according to an embodiment of the present invention, and transmits disk data or a disk image to the diskless terminal 100.

FIG. 11 is a flowchart illustrating a diskless operation method according to an embodiment of the present invention, wherein the diskless management server 200 performs the disk management method described with reference to FIGS. 1 to 9.

Referring to FIG. 11, the diskless terminal 100 requests a boot from the diskless management server 200 (S601).

The diskless management server 200 checks at least one previously stored incremental disk (S603) and determines whether a virus or ransomware infection has occurred (S605). At this time, if it is determined that an infection has occurred, the incremental disk that is infected is removed (S607).

The diskless management server 200 generates a new incremental disk of the next layer (S609). In operation S613, boot information or a boot image is generated and transmitted to the diskless terminal 100. Then, the diskless terminal 100 selects boot information (S615).

In this case, the boot information may be selected from a plurality of incremental disks to boot into a backup environment.

The diskless terminal 100 boots with the selected boot information (S617) and accesses the selected incremental disk (S619).

Thereafter, the read and write of the diskless terminal 100 are performed in incremental disk units (S621 and S623).

When the diskless management server 200 ends the incremental disk connection from the diskless terminal 100 (S625), the diskless management server 200 checks the terminated incremental disk (S627). As a result of the test, it is determined whether an infection occurs (S629). If it is determined that an infection has occurred, the incremental disk is removed (S631).

Steps S601 to S615 described so far correspond to a pre-boot execution environment (PXE) state. Step S617 corresponds to the booting state. Steps S619 to S623 correspond to the use state. S625 corresponds to the end state.

12 illustrates a boot screen according to an embodiment of the present invention.

Referring to FIG. 12, as a boot screen 500 that the diskless management server 200 outputs to the diskless terminal 100 at boot time, a message indicating whether a virus or ransomware is infected is output, and a boot item 501 is displayed. , Recovery item 503 and backup item 505. That is, as described above, when the computer device or the diskless management server 200 is detected as infected, the user may be notified and the operation according to the user selection may be performed before the incremental disk is removed.

13 is a hardware configuration diagram of a computer device for performing disk management according to an embodiment of the present invention. Here, the computer device may be a computer device having a disk or a diskless management server.

Referring to FIG. 13, computer device 600 is comprised of hardware including a storage device 601, a memory device 603, a processor 605, and a communication device 607 and is coupled to and executed in hardware at a designated location. Stored program is saved.

The hardware has the configuration and performance to implement the method of the present invention. The operation method of the present invention described with reference to FIGS. 1 to 12 is written as a software program in a program language. The program includes instructions for executing the present invention in combination with hardware such as storage device 601, memory device 603, processor 605, and the like.

The storage device 601 may include a hard disk, a compact disk read only memory (CD-ROM), a CD rewritable (CD-RW), a digital video disk ROM (DVD-ROM), a DVD-RAM, a DVD- It may be implemented as a permanent or volatile storage device such as an optical disk such as a rewritable disk, a blue-ray disk, flash memory, various types of RAM, the above-described physical disk, the base disk and at least one Include incremental disks.

The memory device 603 may be a RAM such as dynamic random access memory (DRAM), rambus DRAM (RDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), or the like. It may be implemented in a medium.

The processor 605 may be implemented with a central processing unit (CPU) or other chipset, microprocessor, or the like.

The communication device 607 allows the memory device 603 and / or the processor 603 to access the network.

As described above, according to the embodiment of the present invention, unlike the conventional operation without the driver (Driver) loading on the operating system (OS), even if a virus infection in the operating system (OS), there is no problem due to the driver non-driven, It is possible to drive a computer device regardless of system (OS) operation.

In addition, since backup and restore are performed in incremental disk units independent of the base disk on which the operating system (OS) is installed, the backup and restore may be performed before the operating system (OS) is booted. Therefore, when the operating system (OS) file is damaged, it is possible to solve the conventional problem that the operating system (OS) does not boot and difficult to backup and restore.

In addition, it is possible to determine the virus infection and ransomware infection through the size of the incremental disk, the file scan, and restore to the state before the virus by restoring to the previous incremental disk.

The embodiments of the present invention described above are not only implemented through the apparatus and the method, but may also be implemented through a program for realizing a function corresponding to the configuration of the embodiments of the present invention or a recording medium on which the program is recorded.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

Claims (13)

As a disk management method of a computer device,
Creating an underlying disk with the operating system stored and set to a user-specified state,
Creating a new incremental disk for storing data according to an operation of the operating system, referring to a logical address not used in a previously created incremental disk among the entire logical addresses representing the storage space of the base disk, and
Managing the base disk and the plurality of incremental disks in a hierarchical structure according to a generation order, and performing backup or restore in incremental disk units;
The performing of the restoration may include:
And removing at least one incremental disk consecutive from a part selected layer among the plurality of layered incremental disks and restoring to an incremental disk corresponding to the selected layer. delete In claim 1,
The performing of the restoration may include:
Checking the incremental disk to see if the difference between the incremental disk size of the top tier and the incremental disk size one tier below the top tier is greater than a predefined threshold, and
If the threshold value is greater than or equal to the threshold value, removing the highest-level incremental disk by determining that the virus or malware is infected
Including, the disk management method. In claim 1,
The performing of the restoration may include:
Checking the files of at least one predefined format stored on the incremental disk, and
If the files of the predefined format are above a predetermined threshold or the file header format is not a registered format, determining that the file is a ransomware infection and removing the corresponding incremental disk;
Including, the disk management method. In claim 1,
The performing of the restoration may include:
If the file name and file path stored on the incremental disk are a predefined special path, the virus is determined to be infected and the corresponding incremental disk is removed.
Including, the disk management method. In claim 1,
The step of performing the backup,
Selectively backing up the entire incremental disk or incremental disks from the top tier to any previous tier according to policy, among a plurality of incremental disks created at each boot
Including, the disk management method. In claim 1,
The step of creating a new incremental disk,
Creating a new incremental disk at boot time referring to an unused logical address in a previously created incremental disk of the total logical addresses,
De-reference of the logical address used to store data among the logical addresses referenced by the new incremental disk, and
Allocating disk space corresponding to the dereferenced logical address as storage space of the incremental disk independently of the base disk;
Including, the disk management method. A disk management method of a diskless management server connected to a diskless terminal through a network,
When the boot request is received from the diskless terminal, generating an incremental disk referencing a logical address not used in a previously generated incremental disk among the entire logical addresses indicating the storage space of the base disk,
Transmitting booting information including operating system information and incremental disk information to the diskless terminal;
Executing booting according to the booting information and storing data according to an operation of the operating system on the generated incremental disk, and
Managing the base disk and the plurality of incremental disks in a hierarchical structure according to a generation order, and performing backup or restore in incremental disk units;
The performing of the restoration may include:
And removing at least one incremental disk consecutive from a part selected layer among the plurality of layered incremental disks and restoring to an incremental disk corresponding to the selected layer. In claim 8,
Prior to creating the incremental disc,
Checking the previously created incremental disk, and
Among the previously created incremental disks, if the disk capacity is greater than or equal to a predefined threshold, if files of a specific format are greater than or equal to a predefined capacity, the file header format is not a registered format, and the stored file name and file path are predefined. If at least one of the special path cases is included, further comprising: removing an incremental disk of a corresponding layer or an incremental disk of at least one layer consecutive from the corresponding layer;
The generating step,
And creating the incremental disk in the next layer of the removed layer. In claim 8,
After the storing step,
Checking the incremental disk, and
If the disk size is greater than or equal to the predefined threshold, if the files in a particular format are greater than or equal to the predefined capacity, if the file header format is not a registered format, and if the saved file name and file path are predefined special paths, If at least one of the following is true, removing the scanned incremental disk
The disk management method further comprising. A storage device including a physical disk, an underlying disk, and a plurality of incremental disks,
A memory device for storing a program for managing the base disk and the plurality of incremental disks in a hierarchical structure according to a generation order; and
A processor configured to execute the program in association with the storage device and the memory device;
The plurality of incremental disks,
Refer to each logical address of the entire logical addresses of the base disk, and data according to an operation of an operating system is stored,
The program,
Perform booting using the base disk, create the incremental disk before the boot or end the boot, perform the backup in incremental disk units, and at least one consecutive from a selected layer among a plurality of layered incremental disks And instructions for removing an incremental disk of a to perform a restore to an incremental disk corresponding to the selected layer. In claim 11,
The program,
Among the plurality of incremental disks, if the disk capacity is greater than or equal to a predefined threshold, if files of a specific format are greater than or equal to a predefined capacity, if the file header format is not a registered format, and the stored file name and file path are predefined Instructions for performing a restore by removing an incremental disk of a layer corresponding to at least one of the path cases or an incremental disk of at least one layer consecutive from the corresponding layer. In claim 11,
The program,
Selecting among the plurality of incremental disks the entire incremental disk or an incremental disk from the top layer to any previous layer as a backup destination, and removing the remaining unselected incremental disks according to the policy.

Images