KR20100124377A - Web hard server and data synchronization method thereof - Google Patents
Web hard server and data synchronization method thereof Download PDFInfo
- Publication number
- KR20100124377A KR20100124377A KR1020090043336A KR20090043336A KR20100124377A KR 20100124377 A KR20100124377 A KR 20100124377A KR 1020090043336 A KR1020090043336 A KR 1020090043336A KR 20090043336 A KR20090043336 A KR 20090043336A KR 20100124377 A KR20100124377 A KR 20100124377A
- Authority
- KR
- South Korea
- Prior art keywords
- synchronization
- data
- web hard
- hard server
- storage device
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/163—Interprocessor communication
- G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
- G06F15/17306—Intercommunication techniques
- G06F15/17325—Synchronisation; Hardware support therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Mathematical Physics (AREA)
- Software Systems (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
The present invention relates to a web hard server, and more particularly, to a web hard server capable of synchronizing data with another storage device and a method of synchronizing data thereof.
Web hard server (Web hard server) is a device that can easily manage the data of the user by assigning a certain storage space to the user of a personal computer connected via a network such as the Internet. That is, the user can access a website (or a server managing the webpage) corresponding to the web hard server using a personal computer, and the user's data (for example, image data, video data, Music data, document data, etc.) can be stored and viewed, and can be easily modified and deleted.
The web hard server enables users to manage data more efficiently. For example, an individual user can upload his or her personal data to the web hard server or stored in the web hard server regardless of the location. Users can easily manage their personal data by downloading their own data, and corporate users can easily share data among employees by using the web hard server and easily transfer business data to traders.
By the way, when the operator and the user of the web hard server has a relationship with each other, the operator receives a certain fee from the user and allocates a storage space corresponding to the fee to the user, such a web hard server may cause a security problem. For example, if a user of a web hard server operated by another person (hereinafter referred to as a leased web hard server) uploads confidential data to the web hard server, hacking by a competitor may be prevented. Except for this, there is a possibility that the confidential data is exposed to the outside by the rented web hard server administrator.
Therefore, recently, an installable web hard server in which a user directly runs a web hard server has appeared. In other words, recently, a web hard server has been introduced that a company, a government agency, a university or an individual can build a web hard solution on its own server and operate the user himself.
By the way, while the installation-type web hard server has an advantage over the lease-type web hard server in security, there is a problem that there is no means that can be synchronized between a plurality of installed web hard server. For example, there was a problem in that the installed web hard server operated by the corporate headquarters and the installed web hard server operated by the branch of the company cannot be automatically synchronized with each other.
As a result, a problem may occur in which data sharing between the head office and the instruction is not easily performed, and in addition, the user may prepare for a failure in the installed web hard server (that is, when data stored in the installed web hard server is lost). Inconvenience of having to have a separate backup storage device may occur.
The present invention has been made to solve the above-described problems, to provide a web hard server and a data synchronization method capable of automatically synchronizing a plurality of web hard servers.
In addition, the present invention is to provide a web hard server and a method for synchronizing data that does not need to be provided with a separate backup storage device in case the data stored in the web hard server is lost.
According to an aspect of the present invention, a synchronization processor for transmitting an m-th synchronization command to a storage device connected through a network when the m-th event occurs; And a data storage unit for storing the m-th transmission target data received from the storage device in response to the m-th synchronization command, wherein m is a natural number.
Here, the synchronization processor may delete the m-th deletion target data from the data storage unit according to the m-th synchronization information received from the storage device in response to the m-th synchronization command.
The web hard server may further include a controller configured to store the m-th transmission target data in the data storage and to generate an m + 1th event when a preset time elapses.
According to another embodiment of the present invention, the m-th synchronization information on the data updated after the m-th synchronization is generated according to the m-th synchronization command, and the m-th transmission target data corresponding to the m-th synchronization information is detected. A synchronization processor; And a communication unit for transmitting the m-th synchronization information and the m-th transmission target data to a storage device connected through a network, wherein m is a natural number.
Here, the m-th synchronization command may be received from the storage device.
The web hard server may further include a controller configured to generate an m + 1th synchronization command when the m-th transmission target data is transmitted to the storage device and a preset time elapses.
According to another embodiment of the present invention, a method of synchronizing data with another storage device in a web hard server, the method comprising: transmitting an m-th synchronization command to a storage device connected through a network when an m-th event occurs; Receiving m-th transmission target data from the storage device in response to the m-th synchronization command; And storing the m-th transmission target data in a storage space provided with the m-th transmission target data, wherein m is a natural number.
The data synchronization method may further include deleting m-th deletion target data from the storage space according to m-th synchronization information received from the storage device in response to the m-th synchronization command.
The data synchronization method may further include generating the m + 1th event when the m th transmission target data is stored in the storage space and a predetermined time elapses.
According to another embodiment of the present invention, in a method of synchronizing data with another storage device in a web hard server, generating m-th synchronization information on data updated after m-1 synchronization according to an m-th synchronization command step; Detecting m-th transmission target data corresponding to the m-th synchronization information; And transmitting the m-th synchronization information and the m-th transmission target data to a storage device connected through a network, wherein m is a natural number.
The generating of the m th synchronization information may include receiving the m th synchronization command from the storage device.
The data synchronization method may further include generating an m + 1th synchronization command when the m-th transmission target data is transmitted to the storage device and a preset time elapses.
According to still another embodiment of the present invention, there is provided a computer-readable recording medium having recorded thereon a program for executing the data synchronization method according to any one of claims 7 to 12 on a computer.
According to the web hard server and the data synchronization method according to the present invention, a plurality of web hard servers can be automatically synchronized with each other.
In addition, according to the web hard server and the data synchronization method according to the present invention, there is no need to provide a separate backup storage device in case the data stored in the web hard server is lost.
In addition, according to the web hard server and the method for synchronizing data thereof according to the present invention, a backup storage device is not required in case a separate data of the web hard server is lost, thus saving the cost of the backup storage device.
As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all transformations, equivalents, and substitutes included in the spirit and scope of the present invention. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.
The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
1 is a schematic configuration diagram of a web hard system according to an embodiment of the present invention.
Referring to Figure 1, the web
The
The web hard server 130-n stores data received from the
2 is a schematic block diagram of a web hard server according to an embodiment of the present invention.
2, the web hard server 130-n according to an embodiment of the present invention is a
Here, for convenience of understanding and explanation, the web hard server 130-n shown in FIG. 2 is referred to as an n th web hard server 130-n, and is a synchronization target with the n th web hard server 130-n. The server is referred to as a p-th web hard server 130-p. Here, components of the p th web hard server 130-p may be the same as or similar to the n th web hard server 130-n. In addition, only the operation for synchronizing data with the n-th web hard server 130-n and the p-th web hard server 130-p will be described in detail below.
The
In addition, the
The subscriber
The
The
In addition, when the m-th synchronization information transmitted from the p-th web hard server 130-p is input through the
In this case, the newly updated data may include data newly stored in the p web hard server 130-p and / or data deleted from the p web hard server 130-p after the m-1 synchronization. The m synchronization information may include information on the data corresponding to the former (hereinafter referred to as m-th transmission object data) and / or data corresponding to the latter (hereinafter referred to as m-th deletion subject data). Therefore, the
In addition, when the m-th transmission target data is received from the p-th web hard server 130-p, the
In addition, the
The
In addition, the
For another example, if the
In the above, the operation of the n-th web hard server 130-n generating the m-th synchronization command and transmitting it to the p-th web hard server 130-p has been described. Hereinafter, the case where the n-th web hard server 130-n receives the m-th synchronization command from the p-th web hard server 130-p will be described.
That is, when the
In addition, the
That is, the
Herein, it is assumed that the m-th synchronization command is received from the p-th web hard server 130-p. However, the m-th synchronization command may be generated by the
For example, the
For another example, the
That is, the m-th synchronization command may be transmitted from the p-th web hard drive 130-p to the n-th web hard server 130-n, or may be generated by the n-th web hard server 130-n itself. have.
3 is an exemplary diagram for a data synchronization setting operation in a web hard server according to an embodiment of the present invention.
Referring to FIG. 3, a display unit (not shown in FIG. 2) of the n-th web hard server 130-n is illustrated. The display unit (not shown) includes a
Therefore, the operator of the n-th web hard server 130-n operates an input unit (not shown) to input the domain address of the p-th web hard server 130-p to be synchronized to the
As illustrated in FIG. 3, the n-th web hard server 130-n performs synchronization every three hours with the p-th web hard server 130-p whose domain address corresponds to idv.officehard.biz. Among the folders included in the
As described above, the n-th web hard server 130-n may automatically synchronize data with a preset p-th web hard server 130-p. The data deleted from the nth web hard server 130-n by transmitting the m th synchronization information and / or the m th transmission target data to the p web hard server 130-p is the p th web hard server 130-p. In addition, it can be deleted, and the data newly stored in the n-th web hard server (130-n) can be newly stored in the p-th web hard server (130-p).
In addition, the above description has been made on the assumption that there is only one web hard server (i.e., p-th web hard server 130-p) to be synchronized. Obviously there can be multiple web hard servers. That is, the web hard server to be synchronized with the n-th web hard server 130-n is the p-th web hard server 130-p and the first web hard server 130-l (where l is smaller than n). It is a natural number that is not the same as p), the first web hard server (130-l) performs the same or similar operations as the p web hard server (130-p) n-th web hard server (130-n) ) Can be synchronized.
Accordingly, since the plurality of web hard servers 130-n may be completely synchronized with each other, a separate backup device is not required in case the data stored in the web hard servers 130-n is lost. It is obvious that the user can easily share data between the head office and the branch office.
4 is a flowchart illustrating a data synchronization method in a web hard server according to an embodiment of the present invention.
Hereinafter, a data synchronization method in the web hard server 130-n according to an embodiment of the present invention will be described with reference to FIG. 4. Here, a method of synchronizing data between the first web hard server 130-1 and the second web hard server 130-2 will be described. Each step to be described below may be a step performed by each component included in the first web hard server 130-1 or the second web hard server 130-2, but for convenience of understanding and description. For this purpose, the first web hard server 130-1 or the second web hard server 130-2 will be collectively described.
In operation S410, when the m th event occurs according to a preset condition in the first web hard server 130-1, the first web hard server 130-1 generates the m th synchronization command to generate the second web hard server. Transmit to step 130-2 (step S420). For example, assume that the first web hard server 130-1 is set in advance to generate the m-th synchronization command every three hours. In this case, the first web hard server 130-1 generates an m-th synchronization command when 3 hours have elapsed after the m-1 synchronization ends (that is, when the m-th event occurs). It can transmit to (130-2).
In operation S430, the second web hard server 130-2 having received the m-th synchronization command generates the m-th synchronization information on the newly updated data after the m-1 synchronization is completed. That is, the second web hard server 130-2 may delete data (ie, m-th deletion target data) and / or uploaded data (ie, m-th transmission target data) deleted after m-1 synchronization ends. The m-th synchronization information corresponding to the information may be generated.
In operation S440, the second web hard server 130-2 transmits the generated m-th synchronization information to the first web hard server 130-1. In this case, the m-th synchronization information may be information generated by XML.
In operation S450, the first web hard server 130-1 deletes the m th deletion target data from the storage space provided with the m th synchronization information. That is, the m-th synchronization information may include information about the name, deleted time, size, attributes, etc. of the m-th deletion target data, so that the first web hard server 130-1 analyzes the m-th synchronization information and deletes the m-th synchronization information. The target data may be deleted from the
In operation S460, the second web hard server 130-2 reads from the storage space provided with the m th transmission target data and transmits the read data to the first web hard server 130-1. That is, since the m-th synchronization information includes information on the m-th transmission target data, the second web hard server 130-2 reads it from the storage space provided with the m-th transmission target data corresponding to the m-th synchronization information. To the first web hard server 130-2.
In operation S470, the first web hard server stores the m-th transmission target data transmitted from the second web hard server 130-2 in the storage space provided therein. This is because the m-th transmission target data is newly uploaded data to the second web hard server 130-2 after m-1 synchronization and thus is not stored in the first web hard server 130-1. Here, it is apparent that step S460 and step S470 may be omitted when the m-th transmission target data does not exist.
In operation S480, the first web hard server 130-1 generates the m th synchronization completion signal and transmits the m th synchronization completion signal to the second web hard server 130-2 when the m th transmission target data is normally stored in the storage space. . As a result, the second web hard server 130-2 may recognize that the m-th synchronization is normally completed.
In operation S490, the first web hard server 130-1 generates m-th synchronization end time information for the time at which the m-th synchronization ends, and stores it in the provided storage space. This is because the m + 1th event may be preset from the time at which the mth synchronization ends. In addition, to allow the operator to recognize the time when the m-th synchronization is completed.
In operation S495, when the m-th synchronization completion signal is received, the second web hard server 130-2 ends the m-th synchronization because the m-th synchronization is completed normally.
In the above, the first web hard server 130-1 generates an m-th event, generates an m-th synchronization command, and transmits the m-th synchronization command to the second web hard server 130-2. However, as described above, it is obvious that the m-th synchronization command may be generated by the second web hard server 130-2 in which the m-th synchronization information is generated. In this case, steps S410 and / or S420 described above may be performed by the second web hard server 130-2.
In addition, in FIG. 4, it is assumed that there is only one web hard server (ie, the second web hard server 130-2) to be synchronized with the first web hard server 130-1. Obviously, the hard server 130-1 and the web hard server to be synchronized may be plural. That is, the web hard server to be synchronized with the first web hard server 130-1 may be the second web hard server 130-2 and the third web hard server 130-3, and the third web hard server The server 130-1 may be synchronized with the first web hard server 130-1 by performing the same or similar steps as the second web hard server 130-2.
The data synchronization method of the web hard server according to the present invention described above may be embodied as computer readable codes on a computer readable recording medium. Computer-readable recording media include all kinds of recording media having data stored thereon that can be decrypted by a computer system. For example, there may be a read only memory (ROM), a random access memory (RAM), a magnetic tape, a magnetic disk, a flash memory, an optical data storage device, and the like. In addition, the computer-readable recording medium may be distributed and executed in a computer system connected to a computer network, and may be stored and executed as a code readable in a distributed manner.
In addition, while the above has been described with reference to a preferred embodiment of the present invention, those skilled in the art to which the present invention pertains without departing from the spirit and scope of the present invention as set forth in the claims below. It will be understood that various modifications and changes can be made.
1 is a schematic configuration diagram of a web hard system according to an embodiment of the present invention.
Figure 2 is a schematic block diagram of a web hard server according to an embodiment of the present invention.
3 is an exemplary diagram for a data synchronization setting operation in a web hard server according to an embodiment of the present invention.
4 is a flowchart illustrating a data synchronization method in a web hard server according to an embodiment of the present invention.
<Description of the symbols for the main parts of the drawings>
100: Web hard system
110: user terminal
120: Internet (network)
130-n: Web Hard Server
210: communication unit
220: subscriber information storage
230: data storage
240: synchronization processing unit
250: control unit
Claims (13)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020090043336A KR20100124377A (en) | 2009-05-19 | 2009-05-19 | Web hard server and data synchronization method thereof |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020090043336A KR20100124377A (en) | 2009-05-19 | 2009-05-19 | Web hard server and data synchronization method thereof |
Publications (1)
Publication Number | Publication Date |
---|---|
KR20100124377A true KR20100124377A (en) | 2010-11-29 |
Family
ID=43408588
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
KR1020090043336A KR20100124377A (en) | 2009-05-19 | 2009-05-19 | Web hard server and data synchronization method thereof |
Country Status (1)
Country | Link |
---|---|
KR (1) | KR20100124377A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20170046901A (en) * | 2015-10-22 | 2017-05-04 | 삼성에스디에스 주식회사 | Method for synchronizing of dictionary of deduplication |
-
2009
- 2009-05-19 KR KR1020090043336A patent/KR20100124377A/en not_active Application Discontinuation
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20170046901A (en) * | 2015-10-22 | 2017-05-04 | 삼성에스디에스 주식회사 | Method for synchronizing of dictionary of deduplication |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109040252B (en) | File transmission method, system, computer device and storage medium | |
CN101193075B (en) | Method and apparatus for managing blog information | |
US9864736B2 (en) | Information processing apparatus, control method, and recording medium | |
US20150227605A1 (en) | Information processing terminal, synchronization control method, and computer-readable recording medium | |
CN107656695B (en) | Data storage and deletion method and device and distributed storage system | |
CN109361525B (en) | Method, device, control terminal and medium for restarting distributed deployment of multiple services | |
CN105338048A (en) | File transmission method and system under virtual desktop infrastructure | |
CN103873519B (en) | A kind of method of data synchronization, client, server, terminal and system | |
US10855746B2 (en) | Generating content fragments for content distribution | |
CN108885671A (en) | A kind of directory delete method, apparatus and storage server | |
CN103368991A (en) | Cloud storage immediate synchronization system | |
CN108063879A (en) | Remote support system and its control method support device, information processing unit and medium | |
EP3444722A1 (en) | Installation of operating system | |
US20150020167A1 (en) | System and method for managing files | |
CN109726039B (en) | Method and apparatus for managing virtual machines | |
CN103368990A (en) | Cloud storage immediate synchronization method | |
CN112615909A (en) | Method for storing data in cascade storage server cluster and related equipment | |
JP5552720B2 (en) | Storage system, storage server, user data sharing method, and program | |
KR20100124377A (en) | Web hard server and data synchronization method thereof | |
JP2010009462A (en) | Server-client system and server switching method thereof | |
CN103581182A (en) | Web message releasing method and device | |
US20160117135A1 (en) | Apparatus and method for processing information on file or job | |
JP5343453B2 (en) | Content file management system | |
US9979787B2 (en) | Information processing system, network storage device, and non-transitory recording medium | |
US10628220B2 (en) | Information processing system, information processing method, and non-transitory computer-readable storage medium for storing program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
A201 | Request for examination | ||
E902 | Notification of reason for refusal | ||
E601 | Decision to refuse application |