KR20230173351A - Data integrated management system with server redundancy for data management, shared storage delivery, and data backup services - Google Patents

Abstract

The present invention relates to a data integrated management system that manages data through server duplication, provides storage for sharing the data, and enables backup services for the data according to a preset backup schedule. will be. The data integrated management system capable of managing data through server duplication, providing shared storage, and data backup services according to the present invention provides a data integration management module that manages data in the server through server duplication, and a network drive to a plurality of user terminals. , a network drive module that allows the user terminal to access data managed by the data integrated management module through the network drive, and a backup module that backs up data managed by the data integrated management module according to a preset schedule. Includes.

Description

Data integrated management system capable of data management through server duplication, provision of shared storage, and data backup services {DATA INTEGRATED MANAGEMENT SYSTEM WITH SERVER REDUNDANCY FOR DATA MANAGEMENT, SHARED STORAGE DELIVERY, AND DATA BACKUP SERVICES}

The present invention relates to a data integration management system, and more specifically, data integration that manages data through server duplication, provides storage for sharing the data, and enables backup services for the data according to a preset backup schedule. It's about management systems.

In general, most work in companies is performed using computers. The results of the work are created as files (Word, Powerpoint, CAD, etc.). In order to increase collaboration and security for business files created at this time, the server's storage space is provided to the user terminal as a network drive, and the user creates business files on the network drive in the user terminal. Technologies for storing, modifying, and sharing are attracting attention.

Meanwhile, a centralized storage system exists for at least one server. The server connects to a storage system connected to a communication network and writes or reads data. At this time, if one of the servers connected to each other fails, the data in the failed server cannot be used, causing great inconvenience. Therefore, there is an emerging need for an integrated data management system that stores the same data redundantly on different servers and allows access to the data even when a server fails.

Meanwhile, so-called server duplication, which stores the same data redundantly on different servers, has the problem that accidentally reflected data or virus-infected files can also be copied. Therefore, the need for a backup system that can restore data that has been accidentally reflected or files infected with viruses is also emerging.

Republic of Korea Patent Publication No. 10-2084031 (announced on May 29, 2020)

The purpose of the present invention to solve the above-mentioned problems is to access data managed through server duplication through a network drive mounted in the user terminal, and data management through server duplication to restore data managed through server duplication. , to provide an integrated data management system capable of providing shared storage and data backup services.

In order to achieve the above-mentioned purpose, a data integrated management system capable of data management, shared storage provision, and data backup service through server duplication according to an embodiment of the present invention is a data integration management system that manages data within the server through server duplication. module, a network drive module that provides a network drive to a plurality of user terminals and allows the user terminal to access data managed by the data integration management module through the network drive, and a network drive module managed by the data integration management module. Includes a backup module that backs up data according to a preset schedule.

At this time, the data integration management module includes a plurality of servers, each of the plurality of servers includes a local storage, the data integration management module groups the local storage, and the local storage in the same group contains the same data. The data integration management module is configured to provide data stored on another server in the same group as the at least one server to the user terminal when a failure occurs in at least one of the plurality of servers. Ensures the stability of data use of the user terminal.

In addition, the network drive module includes a drive agent unit that provides a network drive to the user terminal and a shared storage unit that allows the user terminal to access local storage of a plurality of servers included in the data integration management module through the network drive. It includes, wherein the drive agent unit, when the user terminal transmits a signal requesting reception of data stored in the server in which the error occurred, provides data stored in another server in the same group as the server in which the error occurred to the user terminal, so that the user Ensures the stability of data use on the terminal.

Meanwhile, the shared storage unit receives and stores data stored in the local storage, the drive agent unit converts the data stored in the shared storage unit into a data system of the operating system of the user terminal, and the drive agent unit converts the data stored in the shared storage unit into a data system of the operating system of the user terminal. The data system is provided by mounting it as a network drive of the local operating system for the user terminal, and the drive agent unit allows the user terminal to access the shared storage unit through the network drive to create, modify, or delete data. When performed, the results are reflected in the data in the local storage so that a plurality of user terminals can share the data in the local storage.

And the data integration management module further includes a backup unit that grants access to data in the server according to the preset schedule, and the backup module is configured to select data in the server according to the preset schedule through the backup unit. It includes a backup agent unit that specifies backup target data and forms the designated backup target data into backup data, and a backup storage unit that receives and stores the backup data formed by the backup agent unit.

According to the present inventor's integrated data management system capable of data management through server duplication, provision of shared storage, and data backup service, data managed through server duplication is accessed through a network drive mounted in the user terminal and managed through server duplication. It has the effect of restoring damaged data.

Figure 1 is a diagram showing each module of the data integrated management system capable of data management, shared storage provision, and data backup service through server duplication according to the present invention.
Figure 2 is a diagram showing each configuration of the data integration management module according to the present invention.
Figure 3 is a diagram showing each configuration of the network drive module according to the present invention.
Figure 4 is a diagram showing each configuration of the backup module according to the present invention.
Figure 5 is a diagram showing each configuration of the backup agent unit according to the present invention.
Figure 6 is a diagram showing an embodiment of a server load diagram according to the present invention.
Figure 7 is a diagram showing another embodiment of a server load diagram according to the present invention.
Figure 8 is a diagram showing another embodiment of a server load diagram according to the present invention.

Hereinafter, some embodiments of the present invention will be described in detail through illustrative drawings. When adding reference signs to components in each drawing, it should be noted that the same components are given the same reference numerals as much as possible even if they are shown in different drawings.

Also, in describing embodiments of the present invention, if detailed descriptions of related known configurations or functions are judged to impede understanding of the embodiments of the present invention, the detailed descriptions will be omitted.

Additionally, when describing the components of an embodiment of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are only used to distinguish the component from other components, and the nature, sequence, or order of the component is not limited by the term.

In this specification, singular forms also include plural forms unless specifically stated in the phrase. As used in the specification, “comprises” and/or “including” does not exclude the presence or addition of one or more other components in addition to the mentioned components.

Hereinafter, the present invention will be described in more detail with reference to the attached drawings.

Figure 1 is a diagram showing each module of the data integrated management system 1000 capable of data management, shared storage provision, and data backup service through server duplication according to the present invention.

Referring to FIG. 1, the data integrated management system 1000 (hereinafter referred to as 'system') capable of data management through server duplication, provision of shared storage, and data backup service according to the present invention includes a user terminal 220, It includes a network drive module 200, a data integration management module 100, and a backup module 300. Each module (100, 200, 300) is connected to each other through a wired or wireless communication network. As an embodiment, the user terminal 220 is connected to the network drive module 200, the network drive module 200 is connected to the data integration management module 100, and the data integration management module 100 is a backup module ( 300).

Figure 2 is a diagram showing each configuration of the data integration management module 100 according to the present invention.

The data integrated management module 100 according to the present invention manages data through server duplication with guaranteed high availability (HA) based on virtualization technology. Referring to FIG. 2, the data integration management module 100 includes a plurality of servers 110, 120, 130, and 140 and local storages 111, 121, and 131 included in each server 110, 120, 130, and 140. , 141). Each server (110, 120, 130, and 140) included in the data integration management module 100 is connected to each other to form a physical network. The data integration management module 100 manages the local storages 111, 121, 131, and 141 of each server 110, 120, 130, and 140 by grouping them into groups 101 and 102, and manages the local storages 111 and 102 of the same group. 121, 131, 141) have the same data. That is, the data integration management module 100 groups the local storages 111, 121, 131, and 141 of each server 110, 120, 130, and 140 through a virtual network and manages them in an integrated manner. The data integration management module 100 duplicates the server by storing identical data in the local storages 111, 121, 131, and 141 of each group 101 and 102. The data integration management module 100 immediately provides data stored in another server to the user terminal 220 when a failure occurs in at least one server.

For example, the data integration management module 100 may configure the first local storage 111 of the first server 110 and the second local storage 121 of the second server 120 into the first server group 101. In one case, each data in the first local storage 111 and the second local storage 121 is stored in an alternating manner. That is, when data a is stored in the first local storage 111 and data b is stored in the second local storage 121, the data integration management module 100 stores the data a in the first local storage 111. Data a is copied and stored in the second local storage 121, and data b from the second local storage 121 is copied and stored in the first local storage 111. Accordingly, the first local storage 111 and the second local storage 121 of the first server group 101 store the same data in duplicate. When an inspection or failure of a server occurs, the data integration management module 100 stores the same data in any one of the local storages 111 and 121 of the first server group 101. 121), that is, data stored redundantly in the local storage of another server of the same group can be provided to the user terminal 220, so the stability of data use can be guaranteed. A more detailed description of the data integration management module 100 will be provided later.

Figure 3 is a diagram showing each configuration of the network drive module 200 according to the present invention.

Referring to FIG. 3, the network drive module 200 according to the present invention is a drive agent unit 211 that provides a network drive to the user terminal 220 and a data integration management module through which the user terminal 220 provides a network drive. It includes a shared storage unit 213 that allows access to the local storage (111, 121, 131, 141) of each server (110, 120, 130, 140) included in (100). Meanwhile, at this time, the shared storage unit 213 may be each local storage 111, 121, 131, and 141 of each server 110, 120, 130, and 140 included in the data integration management module 100, and , or it may be a separate storage where the data of each local storage (111, 121, 131, 141) is copied. When the data stored in the shared storage unit 213 is changed, the data in each local storage (111, 121, 131, and 141) of each server (110, 120, 130, and 140) is also changed.

That is, the user terminal 220 accesses each local storage 111, 121, 131, and 141 included in the data integration management module 100 through the network drive provided by the drive agent unit 211 to generate data. When modification, deletion, etc. are performed, the results are reflected in real time in the data of each local storage (111, 121, 131, 141) of the shared storage unit (213) or the data integration management module (100).

Accordingly, a plurality of user terminals 220 can share data in each local storage of the data integration management module 100 through a network drive. A more detailed description of the network drive module 200 will be provided later.

Figure 4 is a diagram showing each configuration of the backup module 300 according to the present invention.

Referring to FIG. 4, the backup module 300 according to the present invention is the local storage (111, 121, 131, 141) in the server (110, 120, 130, 140) managed by the data integration management module 100. Data is backed up according to a preset schedule. The servers 110, 120, 130, and 140 included in the data integration management module 100 further include backup units 113, 123, 133, and 143, respectively. The backup unit 113, 123, 133, and 143 grants access to data in the local storage 111, 121, 131, and 141 to the backup agent unit 311 according to a preset backup schedule. The backup module 300 includes a backup agent unit 311, and the backup agent unit 311 backs up data in the local storage (111, 121, 131, 141) according to a preset schedule. (113, 123, 133, 143) is accessed to back up the data in the local storage (111, 121, 131, 141) to the backup storage unit (313).

On the other hand, server duplication has a problem in that data in each local storage (111, 121, 131, and 141) is stored redundantly in real time, so data accidentally reflected or files infected with a virus may be copied. The backup module 300 can restore accidentally reflected data or virus-infected files by backing up data according to a preset schedule, that is, at intervals. A more detailed description of the backup module 300 will be provided later.

Hereinafter, the data integration management module 100, network drive module 200, and backup module 300 according to the present invention will be described in more detail.

The data integration management module 100 according to the present invention is composed of a plurality of servers 110, 120, 130, and 140 and a physical switch (not shown). A plurality of servers 110, 120, 130, and 140 form a physical network through a physical switch (not shown). The data integration management module 100 may be implemented with at least two or more servers.

Each server (100, 110, 120, 130) may include hardware such as a central processing unit, memory, and interface device, and software such as an operating system and supervisor. Since the general configuration of server hardware and software is widely known, the following will mainly describe the configuration of the server for the data integration management module 100 of this embodiment.

Each server 110, 120, 130, and 140 may or may not include at least one virtual machine. For example, the first to third servers 110, 120, and 130 may each include at least one virtual machine, and the fourth server 140 may not include a virtual machine.

As an embodiment, a plurality of servers (110, 120, 130, and 140) are virtual servers that integrate and manage the local storage (111, 121, 131, and 141) included in each server (110, 120, 130, and 140). Includes machines. Hereinafter, a virtual machine that integrates and manages local storage (111, 121, 131, 141) of multiple servers (110, 120, 130, 140) is referred to as a 'management virtual machine', and other general virtual machines are referred to as 'general virtual machines'. It is called ‘machine’.

The management virtual machine is located on at least one of the plurality of servers 110, 120, 130, and 140, and can be migrated between servers as needed.

Each server (110, 120, 130, 140) has at least one general virtual machine (not shown), a management virtual machine (not shown), local storage (111, 121, 131, 141), a physical port (not shown), and It includes a backup unit (113, 123, 133, 143). The management virtual machine is located in one of a plurality of servers constituting the data integration management module 100.

Local storage (111, 121, 131, 141) is a storage medium such as HDD (Hard Disk Drive) or SSD (Solid State Drive) located within the server (110, 120, 130, 140). Local storage (111, 121, 131, 141) may include at least one HDD or at least one SSD.

Data of the general virtual machine and management virtual machine are stored in local storage (111, 121, 131, 141).

Since the data of the general virtual machine is stored in the local storage (111, 121, 131, 141), if an inspection or failure of the server (110, 120, 130, 140) occurs, the data within the server (110, 120, 130, 140) There is a problem where the operation of the virtual machine is paused. To solve this problem, in this embodiment, at least two or more servers are grouped into server groups (101, 102) to quickly perform migration of virtual machines to provide uninterrupted virtual machine services, and then grouped into server groups (101, 102). ) My data is stored redundantly.

If there are multiple virtual machines in the server (110, 120, 130, 140), a bottleneck may occur in reading/writing data of each virtual machine, or a bottleneck may occur in data transmission and reception with the virtual machine of the external server. . Alternatively, the management virtual machine needs to quickly process control commands or data for managing the local storage (111, 121, 131, 141) of multiple servers (110, 120, 130, 140) without bottlenecks. For rapid data transmission and reception, this embodiment includes a plurality of physical ports.

The physical ports of the servers 110, 120, 130, and 140 are connected to the management virtual machine through a virtual switch (not shown). For example, the management virtual machine can transmit and receive control commands or data for managing the local storage (111, 121, 131, 141) of multiple servers (110, 120, 130, 140) through a physical port.

The physical port is connected to the virtual switch to enable data transmission and reception for virtual machine migration. For example, when the first virtual machine located on the first server 110 migrates to the second server 120, the virtual machine moves through the physical port of the first server 110 and the physical port of the second server 120. Data for machine migration can be transmitted and received.

The physical port is connected to the virtual switch to enable data transmission and reception to the local storage (111, 121, 131, 141). For example, data of a general virtual machine in the server (110, 120, 130, 140) is transmitted and stored in the local storage (111, 121, 131, 141) through a physical port.

A physical port is connected to at least one general virtual machine through a virtual switch.

The backup units 113, 123, 133, and 143 are connected to the backup agent unit 311 of the backup server 310, which will be described later, and are connected to the servers 110, 120, 130, and 140 at the request of the backup agent unit 311. ) of the local storage (111, 121, 131, 141) is granted access to the data in the local storage (111, 121, 131, 141) to the backup agent unit 311 so that the data stored in the local storage (111, 121, 131, 141) can be backed up and stored at regular intervals. The backup unit (113, 123, 133, 143) can back up all data in the local storage (111, 121, 131, 141) every time, or can extract and back up only the data that has changed from the previous backup to the current time. A detailed description of the backup units 113, 123, 133, and 143 and the backup server 310 will be provided later.

In this embodiment, the general virtual machine and the management virtual machine form a virtual network through a virtual switch. For example, general virtual machines and management virtual machines are assigned private IP (Internet Protocol) addresses used in virtual networks, and each virtual machine can transmit and receive data using the private IP address.

For example, when the data integration management module 100 is composed of two servers, the first server 110 and the second server 120, the plurality of servers present in the first server 110 and the second server 120 The regular virtual machines and management virtual machines form a virtual network through at least one virtual switch.

The data integration management module 100 is composed of at least one server group 101 or 102, and each server group 101 or 102 may be composed of at least two servers 110, 120, 130, and 140. As an embodiment, the data integration management module 100 includes a first server group 101 including a first server 110 and a second server 120, a third server 130, and a fourth server 140. ) and consists of a second server group 102 including.

As another example, the number of servers included in each server group may be different. For example, the first server group may be composed of two servers, and the second server group may be composed of three servers.

The management virtual machine integrates and manages multiple server local storages (111, 121, 131, and 141) according to the grouping information of the server group. For example, the management virtual machine determines the resource information of the local storage (111, 121, 131, 141) of the first to fourth servers (110, 120, 130, 140) and then stores it in one integrated storage (111, 121). , 131, 141).

As an embodiment, the management virtual machine stores the data of the general virtual machine redundantly in the local storage (111, 121, 131, 141) within the server group (101, 102). For example, if there is a data write request from the first virtual machine located in the first server 110 of the first server group 101, the management virtual machine sends the data corresponding to the data write request of the first virtual machine to the first server group 101. It is not only stored in the first local storage 111 of the first server 110 where the virtual machine is located, but also in the second local storage of the second server 120 that exists in the same server group 101 as the first server 110 ( 121).

As another example, the management virtual machine may store metadata of the general virtual machine and the management virtual machine redundantly within the server groups 101 and 102. For example, metadata for the first virtual machine of the first server 110 is stored in the first local storage 111 of the first server 110 and the second local storage 121 of the second server 120. It is stored redundantly. As an example, when a virtual machine is created on each server (110, 120, 130, 140), each server (110, 120, 130, 140) is connected to each local within the same server group (101, 102) according to server grouping information. Virtual machine meta information can be stored redundantly in storage (111, 121, 131, 141).

Since the general data and metadata of each virtual machine in the server groups 101 and 102 are stored redundantly, migration of virtual machines within the server groups 101 and 102 can be performed quickly.

As an embodiment, the integrated storage (111, 121, 131, 141), which integrates the local storage (111, 121, 131, 141) of each of the plurality of servers (110, 120, 130, 140), includes general virtual machines and management General data and metadata of the virtual machine are stored. General data refers to various data generated from virtual machine services, and metadata refers to various data that defines a virtual machine, such as virtual machine identifier, virtual machine IP address, and operating system. General data and metadata are redundantly stored in at least two server local storages (111, 121, 131, and 141) for each server group (101, 102).

As an embodiment, the data integration management module 100 includes one server group 101, and the server group 101 includes a first server 110 and a second server 120. The first server 110 has a management virtual machine and first and second general virtual machines, and the second server 120 has third and fourth general virtual machines.

Virtual machine migration may occur in the event of server maintenance or failure. For example, the management virtual machine can periodically send a ping signal to each server to check which server is experiencing a failure.

In one embodiment, when there is an inspection request for the first server 110 or a failure occurs, the management virtual machine is first migrated from the first server 110 to the second server 120. And the first and second general virtual machines of the first server 110 are migrated from the first server 110 to the second server 120. Since data is stored redundantly in the local storages 111 and 121 of the first server 110 and the second server 120, migration can be completed quickly without separate data transmission and reception, enabling uninterrupted provision of virtual machine services. do.

When the inspection of the first server 110 is completed or the problem is resolved, the general virtual machine can be migrated back to the first server 110. At this time, since the data of the general virtual machine remains in the first server 110, only data newly stored by the general virtual machine in the second server 120 can be transmitted to the first server 110.

As an embodiment, the first server group 101 consists of the first server 110 and the second server 120, and the second server group 102 includes the third server 130 and the fourth server 140. ), and when an inspection or failure of the first server group 101 occurs, the management virtual machine and general virtual machine existing in the first server group 101 are connected to each server 130, 140 of the second server group 102. Data migrated to and stored in the local storages 111 and 121 of the first server group 101 are stored in the local storages 131 and 141 of the second server group 102.

When the inspection of the first server group 101 is completed or the problem is resolved, the general virtual machine can be migrated back to the first server group 101. At this time, since the data of the general virtual machine remains in the first server group 101, only data newly stored by the general virtual machine in the second server group 102 can be transmitted to the first server group 101.

Next, the network drive module 200 according to the present invention will be described.

The network drive module 200 according to the present invention includes a network drive server 210, and the network drive server 210 includes a drive agent unit 211 and a shared storage unit 213 as described above. .

Meanwhile, the network drive server 210 may be connected to a plurality of user terminals 220 through a wired or wireless communication network. Additionally, the network drive server 210 may be connected to each server 110, 120, 130, and 140 of the data integration management module 100.

The user requests a connection to the network drive server 210 using the user terminal 220, and each storage or shared storage unit 213 of the shared storage unit 213 included in the network drive server 210 according to the user The data in the local storage (111, 121, 131, 141) of each server (110, 120, 130, 140) included in the data integration management module (100) connected to can be provided as a network drive and used.

The network drive server 210 includes a drive agent unit 211 and a shared storage unit 213.

The drive agent unit 211 transmits and receives data between the network drive server 210 and a plurality of user terminals 220. The shared storage unit 213 includes a storage space provided as a network drive according to the user of the user terminal 220, and the storage space at this time is stored in each server 110, 120, and 130 included in the data integration management module 100. , 140) may be a local storage (111, 121, 131, 141). Hereinafter, the description will be made assuming that the data stored in the local storage (111, 121, 131, 141) is stored in the shared storage unit 213, but the shared storage unit 213 itself is stored in the data integration management module 100 described above. It can also be interpreted to mean each local storage (111, 121, 131, 141).

The user terminal 220 according to the present invention is a typical computing terminal used by a user, such as a PC, laptop, netbook, tablet PC, PDA, mobile, or smartphone. The user terminal 220 is equipped with a local storage medium (not shown) for storing data, and a local operating system (OS, not shown) for the terminal is installed and operated in the user terminal 220.

The local operating system (OS) for the terminal provides a data explorer to explore data such as data stored in the local storage medium for the terminal. Data Explorer is a window-type GUI (graphical user interface) type explorer that displays the directory structure in a folder-type hierarchy. Additionally, the local operating system (OS) for the terminal mounts the storage medium as a drive and allows data to be searched using a directory structure.

In other words, in addition to the local storage medium for the terminal, external storage media or storage space on the network can be mounted as a drive. In general, when a storage medium of another computer terminal connected on a network is connected as a drive, it is called a network drive.

The network drive server 210 according to the present invention stores content (hereinafter referred to as ' (referred to as 'data') is provided to the user terminal 220.

The network drive server 210 allows multiple users to perform collaborative work by sharing one data. In other words, when one user checks out the data to use it, the data is set to locked to prevent other users from modifying the data. Additionally, when a user checks in after finishing using the data, the data is unlocked so that other users can use and modify the data.

The network drive server 210 stores and manages data in the shared storage unit 213. The shared storage unit 213 includes a known database, storage, and/or repository.

Meanwhile, data stored or connected to the shared storage unit 213 is managed and accessed through the network drive server 210, or is stored in each local storage unit 111, 121, and As 131 and 141) are approached, data will be stored and managed in the network drive server 210 without mention of the shared storage unit 213.

The network drive server 210 according to the present invention further includes a drive agent unit 211 that allows the user terminal 220 to access data managed by the network drive server 210.

In particular, the drive agent unit 211 allows the shared storage unit 213 to be accessed in the form of a network drive from the user terminal 220. To this end, the drive agent unit 211 converts the data stored in the shared storage unit 213 to the data system 1000 of the operating system of the user terminal 220 (or local operating system for the terminal). The drive agent unit 211 mounts the converted data system 1000 as a network drive of the local operating system for the terminal and provides it. That is, the drive agent unit 211 provides a data sharing server function that can share data with the user terminal 220 through a network drive of the local operating system for the terminal.

The network drive server 210 converts the data stored in the shared storage unit 213 to correspond to the structure of the data system 1000 of the local operating system for the terminal provided by the user terminal 220. In detail, the drive agent unit 211 requests the shared storage unit 213 for a list of data stored in the shared storage unit 213 and receives the list of data. The received data list is assigned a unique identifier (or data ID) for each data, and when specific data is selected, the contents of the specific data can be requested and received from the shared storage unit 213 through the unique identifier of the specific data. .

The local operating system for the user terminal 220 uses a data sharing protocol to share data stored in the shared storage unit 213 connected to the network. At this time, the data sharing protocol is a protocol for handling data stored in another computer terminal through the same interface as the data explorer of one's computer terminal. That is, when the user terminal 220 mounts the shared storage unit 213 as a drive through the data sharing protocol, data can be managed through the same interface as if a local storage medium for the terminal were mounted. As an example, when the local operating system for the terminal is Microsoft's Windows, the data sharing protocol is the Samba (SMB) protocol.

The drive agent unit 211 provides a data sharing server function according to the data sharing protocol, requests mount of the shared storage unit 213 from the user terminal 220 to the drive agent unit 211, and drives the drive agent unit 211. ) mounts the network drive in the data system 1000 structure corresponding to the data list.

The user terminal 220 includes an interface unit 221 that extends the shell of the data explorer of the local operating system for the terminal. The interface unit 221 processes the unique functions of the network drive server 210 in addition to the data system 1000 functions of the local operating system for the terminal. In other words, it processes the data collaboration performance function of the network drive server 210 described above.

The shell of the data explorer of the local operating system for the terminal is an interface program for processing user commands. For example, when you double-click a specific folder in the data explorer using the shell, you move to that folder, or when you select specific data or folder, a context menu related to the selected data is displayed.

The interface unit 221 extends the shell of the data explorer and receives information about data sharing (hereinafter referred to as sharing information) from the drive agent unit 211 and displays it as a context menu. Additionally, the extended shell provided by the interface unit 221 performs tasks such as displaying the lock status as a context menu when data is being edited by another user, or briefly displaying all version information of the data.

Additionally, the extended shell displays the unique functions of the network drive server 210 as a context menu, and when the menu is selected from the context menu, the command is transmitted to the drive agent unit 211. The drive agent unit 211 interprets the command and transmits necessary data to the user terminal 220 according to the command.

Meanwhile, when shared information is received from the drive agent unit 211 in the extended shell, the shared information is transmitted and received by the data sharing protocol. If the local operating system for the terminal is Microsoft's Windows, shared information is transmitted by an NTFS stream, a type of alternate data stream (ADS).

The drive agent unit 211 establishes a data sharing session with the user terminal 220 through a data sharing protocol and shares data in the form of a local data system 1000. That is, the drive agent unit 211 shares data in the shared storage unit 213 of the network drive server 210 in the form of a local data system 1000.

As explained earlier, the data sharing protocol is a protocol for handling data stored in other computer terminals through the same interface as the data explorer of one's own computer terminal. When a storage medium connected to the network is mounted as a drive, it is as if it were a local storage medium for the terminal. You can manage data using the same interface as the mounted one. If the local operating system for the terminal is Microsoft's Windows, the data sharing protocol is the Samba (SMB) protocol.

The drive agent unit 211 functions as a data sharing server according to the data sharing protocol. In the case of Windows, the drive agent unit 211 performs the function of a SMB server, mounts the data of the network drive server 210 in the form of a network drive and shares it as shared data on the network. That is, the drive agent unit 211 connects the data sharing session to the network drive.

The drive agent unit 211 transmits information regarding data sharing (hereinafter referred to as sharing information) to the interface unit 221 and receives a command regarding data sharing (hereinafter referred to as sharing command) from the interface unit 221.

The interface unit 221 displays data sharing information as a data context menu. At this time, the sharing information includes a sharing command, and the interface unit 221 transmits the sharing command selected by the context menu to the drive agent unit 211.

Next, we explain the data sharing function among the unique functions of data management. Functions for sharing data include functions such as check-in/check-out and data locking.

When data is modified, it is stored by version by the network drive server 210. The interface unit 221 displays version-specific information about data as shared information.

When a specific version of the data is selected in the interface unit 221 and requests to be received, the drive agent unit 211 loads the specific version of the data stored in the network drive server 210 and sends it to the user terminal 220. send.

Data can be shared by multiple users and modified by each user. At this time, if multiple users modify and save data at the same time, only the data of the user who finally saved may be saved, and the data of other users may not be saved. Therefore, only one user should be able to modify data at a specific time. For this purpose, check-in/check-out is provided.

The drive agent unit 211 sets the data to a locked state where it cannot be modified when the checkout sharing command is selected among the data sharing information through the interface unit 221, and locks the data when the checkin sharing command is selected. ) Release the state. In other words, when data is set to a locked state, subsequent users cannot access the data, and when a user issues a checkout command for specific data, the data is locked. Therefore, other users cannot view specific data. When the user completes modifying the data, he or she saves the data.

Meanwhile, as described above, when an inspection or failure occurs in any of the servers 110, 120, 130, 140 included in the data integration management module 100 containing data desired by the user, that is, for example, The data a desired by the user is located in the first local storage 111 of the first server 110, and the interface unit 221 of the user terminal 220 is located in the first server 110 as a drive agent unit 211. When you want to receive data and transmit a data reception request signal, if an inspection or failure occurs in the first server 110, the drive agent unit 211 is connected to the shared storage unit 213. Data a contained in the second local storage 121 of the second server 120, which is in the same server group 101 as the first server 110, rather than 110, may be provided to the user terminal 220. Therefore, the system 1000 according to the present invention can guarantee the stability of data use.

Next, the backup module 300 according to the present invention will be described.

The backup module 300 according to the present invention includes a backup server 310, and the backup server 310 includes a backup agent unit 311 and a backup storage unit 313, as described above.

The backup agent unit 311 includes a backup program, and when the backup program is executed, the backup target data in the local storage (111, 121, 131, 141) of the server (110, 120, 130, 140) is stored according to a preset schedule. Specify and form backup data based on the specified backup target data. The backup agent unit 311 transmits the formed backup data to the backup storage unit 313. Meanwhile, the backup program may be provided and executed by the user terminal 220 or may be automatically executed by the backup unit 113, 123, 133, and 143 of the data integration management module 100. As the backup program is provided to the user terminal 220, the user terminal 220 can specify a backup schedule through the backup program. Additionally, when the backup program is executed by the backup unit (113, 123, 133, 143), the backup schedule can be automatically specified by the backup unit (113, 123, 133, 143). The backup schedule designation of the backup units 113, 123, 133, and 143 will be described later.

Data to be backed up is data created, deleted, and modified by the user terminal 220 or the servers 110, 120, 130, and 140 (e.g., document data files, image data files, video data files, and audio data files) and system data files, etc.) may be data files that can be processed within the user terminal 220 or the servers 110, 120, 130, and 140.

The backup storage unit 313 receives backup data from the servers 110, 120, 130, and 140 through the backup agent unit 311 and stores it.

When storing backup data, the backup storage unit 313 creates a copy of the backup data and stores it separately from the original to prepare for the case where the original backup data is damaged or cannot be used.

The backup server 310 executes backup according to a set schedule, detects whether the set capacity among the accumulated backup data is exceeded, compares the creation date of the backup data, and deletes the excess capacity portion of the data created first to spare. By designing it to continuously secure disk space, it automatically performs backups after operating the system (1000) and secures disk space by automatically determining whether the set capacity has been exceeded when disk space is insufficient due to accumulated data.

The backup server 310 generates a plurality of backup data and stores them individually so that the original data can be selectively recovered from the accumulated backup data even if the corresponding backup data is damaged.

Figure 5 is a diagram showing each configuration of the backup agent unit 311 according to the present invention.

Referring to FIG. 5 , the backup agent unit 311 includes a backup memory unit 3111, a backup input unit 3113, a backup control unit 3115, and a backup display unit 3117.

In the backup memory unit 3111, the backup program provided to the user terminal 220 or the backup units 113, 123, 133, and 143 is stored, and is stored in the backup program received from the user terminal 220 or the backup unit 113, 123, 133. , 143) automatically sets the backup schedule, multiple backup data folders, backup pre-processor, backup post-task processor, and whether to terminate the backup after completion, etc. are stored.

The backup input unit 3113 receives a backup program execution command, backup time, process or service to be terminated before running the backup program, and operation of the backup program from the user terminal 220 or the backup unit 113, 123, 133, and 143. It receives a process or service to be executed after termination, a predetermined number of folders for storing backup data, and whether or not the backup agent unit 311 will be automatically terminated after backup.

The backup control unit 3115 reads the backup program execution command and backup schedule received by the backup input unit 3113 from the user terminal 220 or the backup unit 113, 123, 133, and 143, and operates the server ( 110, 120, 130, 140), the backup target data is designated, the designated backup target data is formed as backup data, and the formed backup data is transmitted to the backup storage unit 313.

As an embodiment, when forming designated backup target data into backup data, the backup control unit 3115 not only forms the original backup target data into backup data, but also compresses the backup target data to form backup data. By reducing the capacity of the backup data and delivering it to the backup storage unit 313, the storage space of the backup storage unit 313 can be utilized more efficiently. The backup control unit 3115 allocates a permanent memory space for permanently storing backup data and a general memory space for storing backup data other than permanent storage to the backup storage unit 313, and checks whether the formed backup data is permanently stored. And, if the created backup data needs to be stored permanently, it is stored in a permanent memory space.

As an embodiment, the backup control unit 3115 exceeds the set capacity of the backup data accumulated in the backup storage unit 313, and when deleting the excess portion, only the backup data stored in the general memory space is deleted and the backup data stored in the permanent memory space is deleted. By not deleting backup data separately stored in , it is possible to prevent data that must be retained by the user from being deleted.

The backup display unit 3117 displays the operating status of the backup program driven by the backup control unit 3115 on the display device of the user terminal 220.

As an embodiment, the backup display unit 3117 may display the operating status of the backup program on the taskbar on the user terminal 220 (for example, in the case of a Windows PC, the taskbar at the bottom of the screen, etc.). there is.

As an embodiment, the backup display unit 3117 displays a settings window for entering backup program settings (for example, backup time or a process or service to be terminated before running the backup program) on the user terminal 220. ) can be displayed on the display device.

In one embodiment, the backup display unit 3117 displays the backup program to the user through a pop-up window (i.e., a new window that is suddenly created to display certain contents of a specific website) after the backup program starts or ends. Not only can the driving status of the backup program be informed by visual means, but also by auditory means through a sound reproduction means (for example, an external speaker or a built-in speaker, etc.) provided in the user terminal 220. The operating status can be notified to the user.

The backup control unit 3115 transmits backup data to the backup storage unit 313.

The backup control unit 3115 sets a standard capacity for deleting the backup data previously stored in the backup storage unit 313 and stores it in the backup memory unit 3111, and stores the backup data stored in the backup storage unit 313. The capacity is read, and the reference capacity read from the backup memory unit 3111 is compared with the capacity of the backup data stored in the backup storage unit 313. As a result of the comparison, the backup control unit 3115 determines that when the capacity of the backup data stored in the backup storage unit 313 exceeds the standard capacity, the backup data created first among the backup data stored in the backup storage unit 313 exceeds the set capacity. You can delete as much as one part.

As an embodiment, the backup control unit 3115 determines that the capacity of the backup data stored in the backup storage unit 313 is set to a certain ratio of the available storage capacity of the backup storage unit 313 (for example, the amount of backup data stored in the backup storage unit 313 When the available storage capacity (80%) is exceeded, the creation date among the backup data stored in the backup storage unit 313 is compared and the portion of the data created first that exceeds the capacity is deleted, so that the backup storage unit 313 It can be used to create available storage space for newly incoming backup data.

As an embodiment, when deleting backup data stored in the backup storage unit 313, the backup control unit 3115 deletes a predetermined capacity (for example, 10% of the available storage capacity of the backup storage unit 313, etc.) The backup storage unit 313 can secure available storage space for newly incoming backup data by deleting or deleting an amount equal to the amount of newly incoming backup data.

As an embodiment, the backup control unit 3115, when data other than backup data (for example, video data or image data saved according to the user's needs) is stored in the backup storage unit 313, the backup control unit 3115 performs a backup operation. By reading the standard capacity based on the combined capacity of data other than data and backup data, it is possible to prevent insufficient available storage space for newly incoming backup data.

When the backup time is input from the backup input unit 3113 and a backup time reservation request is received, the backup control unit 3115 sets the backup time input according to the backup time reservation request in the backup memory unit 3111.

As an example, when setting the backup time, the backup control unit 3115 can run the backup program at the same time every day, thereby providing business convenience.

When receiving a designated folder name for storing backup data in a pre-designated folder from the backup input unit 3113 and a request for designated backup settings, the backup control unit 3115 returns the designated folder name entered according to the designated backup setting request. Set in the backup memory unit 3111.

When performing a designated backup, the backup control unit 3115 can store separate backup data for each designated folder and can also allow each folder to be backed up at a different time.

The backup control unit 3115 performs a backup operation of a designated data folder and then adds the date and time to the set value of the folder name where the backup data is stored and stores it, thereby preventing the folder name from being the same during daily cumulative backup and preventing the user from using the same folder name. When restoring backed up data, you can selectively restore it by distinguishing the date and time the backup was created.

When the backup control unit 3115 receives a plurality of folder names from the backup input unit 3113 for storing a pre-designated number of backup data in each pre-designated folder and receives a request for setting up multiple backups, the backup control unit 3115 responds to the request for setting up multiple backups. Multiple input folder names can be set in the backup memory unit 3111.

Meanwhile, the backup unit 113, 123, 133, and 143 according to the present invention analyzes the backup schedule and the load of each server according to the system 1000 according to the present invention, and selects the day of the week when the load of the system 1000 is lowest. The backup schedule can be specified by inputting the time zone and time zone into the backup input unit 3113.

At this time, the server load analysis of the backup unit (113, 123, 133, 143) is, for example, the number of user terminals 220 connected to each server of the data integration management module 100 through the network drive module 200. Alternatively, the number of data request messages sent by the interface unit 221 of the user terminal 220 to the drive agent unit 211 may be comprehensively analyzed. At this time, the number of connected user terminals 220 and the number of data request messages may be derived by analyzing logs within the system 1000.

The backup units 113, 123, 133, and 143 continuously analyze the degree of past server load and transmit the analysis results to the backup control unit 3115.

Figure 6 is a diagram showing an embodiment of a server load diagram according to the present invention.

Referring to FIG. 6, the backup control unit 3115 organizes the degree of server load received from the backup units 113, 123, 133, and 143 in the form of a plurality of cells divided by day of the week and time zone to determine the server load. create a diagram At this time, the cell may be in the form of a plurality of consecutive squares. The server load diagram generated by the backup control unit 3115 may be displayed on the user terminal 220 by the backup display unit 3117 and provided to the user.

The backup control unit 3115 can display a plurality of cells differently depending on the degree of server load. For example, when the server load is low, the cells are colored darkly, and when the server load is large, the cells are colored lightly to display the backup. Unit 3117 can be displayed on the user terminal 220. Meanwhile, the coloring of cells according to each day and time of the server load diagram may have a coloring value according to the degree of server load corresponding to the average value of the degree of server load for days and times of multiple weeks. Alternatively, the server load diagram according to one embodiment may represent the degree of server load in the form of a square pillar with the aforementioned cell as the bottom, and in this case, the degree of server load may be the height of the square pillar. The backup display unit 3117 can display a server load diagram with square column-shaped cells on the user terminal 220.

Meanwhile, in FIG. 6, the horizontal length of each cell is shown to mean 1 hour as an example. For convenience, only the time from midnight to noon from 0:00 AM to 12:00 AM is shown, but the server load is also The shape of each cell can be changed at any time depending on the embodiment. Meanwhile, the backup units 113, 123, 133, and 143 can track and analyze not only the past server load, but also the time required for backup.

The backup control unit 3115 can generate a straight line connecting the centers of cells according to the time zone with the lowest load for each day of the week in the server load chart organized in the form of a plurality of cells, and calculate the length of the generated straight line. .

If the time required for backup of the system 1000 ends within the time of a single cell, as an example, within one hour as the horizontal length of the cell shown in FIG. 6, the backup control unit 3115 I guess it didn't take long.

If it is determined that the backup time will not take a long time, the backup control unit 3115 selects the day and time zone with the shortest length among the lengths of the straight line connecting the center of the cell corresponding to the low load time zone, and selects the day and time zone. You can execute a backup by automatically specifying a backup schedule by entering it into the backup input unit 3113.

For example, as shown in Figure 6, the length of the line segment connecting the center of each cell at 5 AM on Tuesday and Wednesday is 1, and the length of the line segment connecting the center of each cell at 4 AM on Thursday and Friday is 1. If is 1, you can specify a backup schedule to perform backups at 5 a.m. on Tuesdays and Wednesdays and at 4 a.m. on Thursdays and Fridays.

If the past backup time does not take a long time, the backup control unit 3115 finds the length of a line segment connecting consecutive low-load times and selects the one with the shortest length. This is because if the same time zone with a short distance is continuous, the accuracy can be guaranteed that the load in that time zone is low.

Meanwhile, the backup input unit 3113 can receive a backup time zone from the user terminal 220, and the backup time zone input from the user terminal 220 is a line segment of the same length derived according to the calculation of the backup control unit 3115. In this case, you can designate the time zone closest to the entered backup time zone as the backup schedule. That is, if the backup time input from the user terminal 220 is 2:00 AM, the backup control unit (3115) operates between 5:00 AM on Tuesday and Wednesday and 4:00 AM on Thursday and Friday where the line segment length is 1, as shown in FIG. ) can specify a backup schedule by specifying the backup time as 4 a.m. on Thursday and Friday. In this way, when the backup time zone is input from the user terminal 220 and one of the days and time zones with the same line segment length is selected, the backup schedule can be set to perform backup at the designated time zone, that is, at 4 AM on other days of the week.

On the other hand, unlike the above, if the time required for backup of the present system 1000 does not end within the time of a single cell, as an example, within one hour according to the horizontal length of the cell shown in FIG. 6, the backup control unit ( 3115) determines that past backups take a long time.

Figure 7 is a diagram showing another embodiment of a server load diagram according to the present invention.

In this case, when it is determined that the past backup time took a long time, the backup control unit 3115, referring to FIG. 7, calculates the distance of the line segment connecting the centers of the cells in the continuous low-load time zone. This is because the longer the length of the line segment obtained by the backup control unit 3115, the less load can be placed on the system 1000 due to backup.

When the backup control unit 3115 continuously selects cells in the time zone with the lowest load, it first derives the cell in the time zone with the lowest load on each day of the week, and then derives the cell in the time zone with the lowest load after that cell. At this time, when a cell in the lowest load time zone and a cell in the next lowest load time zone are adjacent to each other, the backup control unit 3115 connects the centers of both adjacent cells. Again, the backup control unit 3115 derives a cell in the next low-load time period and determines whether the derived cell is adjacent to both cells whose centers are connected by a line segment. If the derived cell is adjacent to both cells whose centers are connected by a line segment, the centers are connected again, and if it is not adjacent to both cells, the backup control unit 3115 no longer derives the low-load time for the corresponding day of the week.

As described above, when the backup time takes a long time, the center of each cell derived by the backup control unit 3115 is connected as shown in FIG. 7. At this time, the backup control unit 3115 derives how long the past backup time took, and compares the derived backup time with the length of the line segment connecting the center of each cell. If the derived backup time is 2 to 3 hours, Wednesday and Friday of FIG. 7 are excluded from the backup schedule in order to minimize the load on the system 1000 due to backup. This is determined to be excluded because the length of the line segment between the centers of each cell on Wednesday and Friday in FIG. 7 is 2. In addition, 2 AM to 6 AM on Monday, 2 AM to 5 AM on Tuesday, 3 AM to 6 AM on Thursday, and 9 AM to Saturday, including all 2 to 3 hours of the derived backup time. The backup control unit 3115 specifies a backup schedule so that backups are performed at 12:00 AM and between 5:00 AM and 11:00 AM on Sundays, respectively.

Meanwhile, as described above, the backup input unit 3113 can receive a backup time zone from the user terminal 220, and the time zone at which the backup starts can be determined according to the backup time zone input from the user terminal 220. For example, if the backup time input from the user terminal 220 is 2 a.m., backup starts at 2 a.m. on Monday and Tuesday, and on Thursday, backup starts at 3 a.m. closest to the input time zone, Backups can start at 9:00 AM on Saturdays and 5:00 AM on Sundays. On the other hand, if the backup time input from the user terminal 220 is 7 a.m., the backup starts at 3 a.m. on Monday so that the backup can be completed at the time closest to 7 a.m., and the backup starts at 2 a.m. on Tuesday. The backup schedule can be set to start at 3:00 AM on Thursday, 9:00 AM on Saturday, and 5:00 AM on Sunday.

Figure 8 is a diagram showing another embodiment of a server load diagram according to the present invention.

Meanwhile, the horizontal length of the cell within the server load may change depending on the time zone input from the user terminal 220. In other words, a weight can be given to the horizontal length of the cell according to the time zone input by the user terminal 220. For example, if the time zone entered by the user terminal 220 is 5 a.m., the horizontal length corresponding to 5 a.m. in the server load diagram may be modified to correspond to twice that horizontal length. When the horizontal length is changed like this, the length of the line segment passing through the center of the cell corresponding to 5 AM is also given a weight of 2, which is an increase of 1. For example, as shown in FIG. 8, as the horizontal length of the cell corresponding to 5 a.m. is doubled, the length of the line segment connected to the center of 5 a.m. also increases, and the backup control unit 3115 increases the length. The above-described calculation is performed based on the line segment. Therefore, the backup schedule can be specified in consideration of the time zone input from the user terminal 220. In the case of Friday, because the length of the line segment in FIG. 7 was 2, backup was not performed on Friday, but as in FIG. 8, the backup schedule was 5 a.m. As the horizontal length of the cell corresponding to the hour increases, the line segment length for Friday becomes 3, so the backup schedule can be changed so that backup is performed on Friday as well.

Meanwhile, the time zone input from the user terminal 220 can receive a plurality of time zones with priorities, and each time zone is lengthened by 5 times, 4 times, 3 times, 2 times, etc. in horizontal length according to the priority. A backup schedule can be specified according to the length of the line segment connecting the center of each cell.

The backup control unit 3115 may check whether the backup program stored in the backup memory unit 3111 is genuine when executing the backup program, and may stop execution of the backup program if the backup program is not genuine.

When executing a backup program, the backup control unit 3115 reads a specific key value stored in the backup storage unit 313 and compares it with the key value of the backup program stored in the backup memory unit 3111, and if the two compared values are different, In this case, an error message is displayed and the execution of the backup program is stopped, preventing illegal copying of the backup program and protecting the rights of the program developer.

The backup control unit 3115, which has the above-described configuration, can store the characteristic key value of the hard disk to determine whether the program is genuine and determine whether to execute it to protect copyright.

The user terminal 220 according to the present invention is a terminal such as a desktop PC, laptop PC, tablet PC, or smartphone equipped with an input means such as a keyboard, mouse, touchpad, or touch screen, and a display screen, and is limited thereto. Instead, it is possible to access the network drive server 210 of the network drive module 200 through a communication network, and process digital information that allows input of search information and selection information, and installation of an application program that can display search result information. All possible configurations can be included. The user terminal 220 according to the present invention is a component that connects to the network drive server 210 through a communication network to transmit and receive information, for example, a smartphone, a tablet personal computer, or a mobile phone. phone, video phone, desktop personal computer, laptop personal computer, netbook computer, personal digital assistant (PDA), portable multimedia player (PMP), wearable device (e.g. : May include at least one of smart glasses, head-mounted-device (HMD), etc.), unmanned terminal (kiosk), or smart watch.

The user terminal 220, network drive module 200, data integration management module 100, and backup module 300 according to the present invention can communicate through each communication unit and communication network. A communication network refers to a connection structure that allows information exchange between nodes such as terminals and servers. Examples of such communication networks include the 3rd Generation Partnership Project (3GPP) network, Long Term Evolution (LTE) network, and 5G. Network, WIMAX (World Interoperability for Microwave Access) network, Internet, LAN (Local Area Network), Wireless LAN (Wireless Local Area Network), WAN (Wide Area Network), PAN (Personal Area Network), wifi network, It includes, but is not limited to, a Bluetooth network, satellite broadcasting network, analog broadcasting network, and DMB (Digital Multimedia Broadcasting) network. The communication unit provided by the user terminal 220, the network drive module 200, the data integration management module 100, and the backup module 300 is provided for the communication network to enable wired and wireless data communication through the above-mentioned communication network. It may include provided electronic components.

In this specification, each component of the network drive module 200, the data integration management module 100, and the backup module 300 may be processors that execute sequential execution processes stored in memory. Alternatively, they may operate as software modules driven and controlled by a processor. Furthermore, a processor may be a hardware device.

The first to fourth local storage units 111, 121, 131, and 141, the shared storage unit 213, and the backup storage unit 313 according to the present invention may include a database management system 1000 (hereinafter referred to as DBMS). there is. DBMS is a set of software tools that allow multiple users to access data in a database. DBMS includes IMS, CODASYL DB, DB2, ORACLE, INFORMIX, SYBASE, INGRES, MS-SQL, Objectivity, O2, Versanat, Ontos, Gemstone, Unisql, Object Store, Starburst, Postgres, Tibero, MySQL or MS-access. can do. DBMS allows access to specific data depending on the input of a specific command.

In this specification, 'part' includes a unit realized by hardware, a unit realized by software, and a unit realized using both. Additionally, one unit may be realized using two or more pieces of hardware, and two or more units may be realized using one piece of hardware.

The scope of protection of the present invention is not limited to the description and expression of the embodiments explicitly described above. In addition, it is to be added once again that the scope of protection of the present invention may not be limited due to changes or substitutions that are obvious in the technical field to which the present invention pertains.

100: Data integration management module 101: 1st server group
102: second server group 110: first server
111: first local storage 113: backup unit
120: second server 121: second local storage
123: Backup unit 130: Third server
131: Third local storage 133: Backup unit
140: fourth server 141: fourth local storage
143: Backup unit 200: Network drive module
210: network drive server 211: drive agent unit
213: shared storage unit 220: user terminal
221: Interface unit 300: Backup module
310: Backup server 311: Backup agent unit
3111: Backup memory unit 3113: Backup input unit
3115: Backup control unit 3117: Backup display unit
313: Backup storage unit
1000: Integrated data management system that enables data management through server duplication, provision of shared storage, and data backup service.

Claims (5)

Data integration management module that manages data within the server through server redundancy;
A network drive module that provides a network drive to a plurality of user terminals and allows the user terminals to access data managed by the data integration management module through the network drive; and
a backup module for backing up data managed by the data integration management module according to a preset schedule;
Including,
An integrated data management system that enables data management through server duplication, provision of shared storage, and data backup services. In claim 1,
The data integration management module includes a plurality of servers,
The plurality of servers each include a local storage,
The data integration management module groups the local repositories and manages local repositories in the same group to have the same data,
The data integration management module, when a failure occurs in at least one of the plurality of servers, provides data stored on another server of the same group as the at least one server to the user terminal to use the data of the user terminal. Characterized by ensuring stability,
An integrated data management system that enables data management through server duplication, provision of shared storage, and data backup services. In claim 2,
The network drive module is,
A drive agent unit that provides a network drive to the user terminal; and
a shared storage unit that allows the user terminal to access local storage of a plurality of servers included in the data integration management module through the network drive;
Includes,
The drive agent unit, when the user terminal transmits a signal requesting reception of data stored in the server in which the error occurred, provides data stored in another server in the same group as the server in which the error occurred to the user terminal, allowing the user terminal to use the data. Characterized by ensuring stability,
An integrated data management system that enables data management through server duplication, provision of shared storage, and data backup services. In claim 3,
The shared storage unit receives and stores data stored in the local storage,
The drive agent unit converts the data stored in the shared storage unit into a data system of the operating system of the user terminal,
The drive agent unit mounts the converted data system as a network drive of the local operating system for the user terminal and provides it,
The drive agent unit, when the user terminal accesses the shared storage unit through the network drive and creates, modifies, or deletes data, reflects the results on the data in the local storage to create a plurality of user terminals in the local storage unit. Characterized by allowing data within the storage to be shared,
An integrated data management system that enables data management through server duplication, provision of shared storage, and data backup services. In claim 1,
The data integration management module further includes a backup unit that grants access to data in the server according to the preset schedule,
The backup module is,
a backup agent unit that specifies backup target data among data in the server according to the preset schedule through the backup unit and forms the designated backup target data as backup data; and
a backup storage unit that receives and stores backup data formed by the backup agent unit;
Including,
An integrated data management system that enables data management through server duplication, provision of shared storage, and data backup services.