KR20100124377A - Web hard server and data synchronization method thereof - Google Patents

Web hard server and data synchronization method thereof Download PDF

Info

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
Application number
KR1020090043336A
Other languages
Korean (ko)
Inventor
조준환
Original Assignee
(주)지란지교소프트
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by (주)지란지교소프트 filed Critical (주)지란지교소프트
Priority to KR1020090043336A priority Critical patent/KR20100124377A/en
Publication of KR20100124377A publication Critical patent/KR20100124377A/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/16Combinations 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/163Interprocessor communication
    • G06F15/173Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
    • G06F15/17306Intercommunication techniques
    • G06F15/17325Synchronisation; Hardware support therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/17Details of further file system functions
    • G06F16/178Techniques for file synchronisation in file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0668Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067Distributed 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

PURPOSE: A web hard server and data synchronization method thereof are provided to remove the necessity of a backup storage device for web hard server by performing automatic synchronization between plural web hard servers. CONSTITUTION: If an event is occurred, a synchronization process unit(240) transmits a sync command to a storage unit connected through network. A data storage module(230) stores data received from the storage unit coping with the sync command. The synchronization process unit deletes the data from the data storage module according to the received sync information from the storage unit. If the fixed time passes after data is saved in the data storage module, a controller(250) creates a next event.

Description

Web hard server and data synchronization method

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 hard system 100 according to an embodiment of the present invention is a user terminal 110 and n web hard servers (130-1, 130-2, 130-n) (where n is Natural number), and the user terminal 110 and the n web hard servers 130-n are connected through a network such as the Internet 120. In FIG. 1, the network is illustrated as the Internet 120. If the user terminal 110 and each of the n web hard servers 130-n are networks that can be interconnected to transmit and receive signals and / or data, the user terminal 110 and the web hard servers 130-n may be applied regardless of the type thereof. Hereinafter, the operation of each component included in the web hard system 100 will be described.

The user terminal 110 accesses the web hard server 130-n and uploads data stored in the user terminal 110 or downloads data stored in the web hard server 130-n. You can get it. For example, the user terminal 110 may access a website corresponding to the web hard server 130-n through the Internet 120, and transmit data to the web hard server 130-n through the web site. You can upload or download. The user terminal 110 accesses the web hard server 130-n and uploads or downloads data, which is obvious to those skilled in the art, and thus a detailed description thereof will be omitted.

The web hard server 130-n stores data received from the user terminal 110 connected to the web hard server 130-n in a storage space provided with the data, or transmits the requested data to the user terminal 110. do. In particular, any web hard server 130-n (where n is a natural number greater than or equal to 2) may synchronize data with another web hard server 130-p (where p is a natural number less than n). Can be. Hereinafter, an operation of synchronizing data with another web hard server 130-p by the web hard server 130-n will be described in detail with reference to FIG. 2.

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 communication unit 210, subscriber information storage unit 220, data storage unit 230, synchronization processing unit 240 and the control unit 250. In addition, although not shown, it is obvious that an input unit (not shown), a display unit (not shown), a power supply unit (not shown), etc. may be further included for the operation of the operator of the web hard server 130-n. In addition, when the web hard server 130-n is an installed web hard server, the web hard server 130-n may further include a website manager (not shown) that manages a website for accessing the web hard server 130-n. .

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 communication unit 210 is a device that performs communication with the user terminal 110 and / or the p-th web hard server 130 -p. For example, the user terminal 110 may transmit data after accessing the n-th web hard server 130-n to store the data stored in the web hard server 130-n. The 210 may output data transmitted from the user terminal 110 to the controller 250.

In addition, the communication unit 210 may transmit the m-th synchronization command (where m is a natural number) input from the synchronization processor 240 to another storage device (ie, the p-th web hard server 130 -p). In addition, the communication unit 210 may transmit the m-th synchronization information received from the p-th web hard server 130-p to the synchronization processor 240 in response to the m-th synchronization command. In addition, the communication unit 210 may transmit the m-th transmission target data received from the p-th web hard server 130-p to the control unit 250. The m-th synchronization command, the m-th synchronization information, and / or the m-th transmission target data will be described in detail later.

The subscriber information storage unit 220 is a memory in which information about the user terminal 110 that can be connected to the n-th web hard server 130-n is stored. For example, in order to access the n-th web hard server 130-n, the user terminal 110 inputs a user ID and / or a password to the n-th web hard server (in particular, the communication unit 210). 130-n, and the n-th web hard server (in particular, the control unit 250) 130-n receiving the received user ID and / or password is stored in the subscriber information storage unit 220. It may be determined whether to allow the connection of the user terminal 110 by determining whether it is stored. Therefore, the user terminal 110 in which the subscriber information (ie, the user ID and / or password) is not stored in the subscriber information storage unit 220 cannot access the n-th web hard server 130-n.

The data storage unit 230 is a memory in which data transmitted to the nth web hard server 130-n is stored. For example, the data transmitted from the user terminal 110 may be received by the communication unit 210 and output to the control unit 250, and the control unit 250 may store the data in the data storage unit 230. .

The synchronization processor 240 generates an m-th synchronization command for data synchronization with the p-th web hard server 130-p connected through the network 120 when the preset m-th event occurs. For example, it is assumed that the operator of the n-th web hard server 130-n is preset to synchronize with the p-th web hard server 130-p at an hourly interval. In this case, when one hour has elapsed after the synchronization setting of the operator, the controller 250 may generate (or generate) a first event and output the same to the synchronization processor 240, and the synchronization processor 240 may input the first input. The first synchronization command may be generated according to the event. Thereafter, the synchronization processor 240 may output the generated first synchronization command to the communication unit 210, and the communication unit 210 may transmit the input first synchronization command to the second web hard server 130-2. have.

In addition, when the m-th synchronization information transmitted from the p-th web hard server 130-p is input through the communication unit 210 in response to the m-th synchronization command, the synchronization processor 240 analyzes the m-th synchronization information. m Deletion target data can be detected. That is, the m-th synchronization information is information generated by the p-th web hard server 130-p. When the m-th synchronization command is input, the p-th web hard server 130-p ends the m-1 synchronization after the m-th synchronization command is input. The m-th synchronization information may be generated by extracting information about newly updated data (for example, the name of the data, the updated time, information about the size or attribute of the data, etc.).

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 synchronization processor 240 may extract information about the m th deletion target data by analyzing the m th synchronization information received from the p th web hard server 130-p, and thus m th deletion target data. May be deleted from the data storage unit 230. As a result, data deleted from the p-th web hard server 130-p may be deleted from the n-th web hard server 130-n. Of course, if the m-th synchronization information does not have information about the m-th deletion target data, it is obvious that the synchronization processing unit 240 does not have to delete the data stored in the data storage unit 230.

In addition, when the m-th transmission target data is received from the p-th web hard server 130-p, the synchronization processor 240 may store the received m-th transmission target data in the data storage 230. Here, the m-th synchronization information may be information generated by Extensible Markup Language (XML), and the m-th transmission target data may be transmitted by an HTP file transfer method.

In addition, the synchronization processor 240 generates the m-th synchronization completion signal to inform the p-th web hard server 130-p that the m-th synchronization is completed when the m-th transmission target data is completed to be stored in the data storage 230. The communication unit 210 may be output to the communication unit 210, and the communication unit 210 may transmit the m-th synchronization completion signal to the p-th web hard server 130-p through a network. As a result, the p th web hard server 130-p may recognize that the m th synchronization is completed normally.

The controller 250 controls the overall operation of the n-th web hard server 130-n. In particular, the controller 250 stores the data transmitted from the communication unit 210 from the user terminal 110 in the data storage 230. In addition, the controller 250 determines whether the user ID and / or password received from the user terminal 110 is stored in the subscriber information storage unit 220 to allow access of the user terminal 110. Can be.

In addition, the controller 250 may generate the m-th event according to a preset method as described above. For example, when the controller 250 is set in advance to generate an event every hour by the operator, the controller 250 may generate the m + 1th event when one hour elapses after the m-th synchronization ends. When the m-th synchronization is terminated, since the m-th synchronization completion signal is generated by the synchronization processor 240, the controller 250 may recognize that the m-th synchronization has ended. Therefore, the controller 250 generates and stores information (hereinafter, referred to as m-th synchronization end time information) about the time point at which the m-th synchronization ends, and then presets a time corresponding to the m-th synchronization end time information. When this elapses, the m + 1th event may be generated. Here, the m-th event may be an arbitrary signal transmitted from the controller 250 to the synchronization processor 240.

For another example, if the controller 250 is preset by the operator to generate an event every hour, the controller 250 may generate the m + 1th event unless the mth synchronization is not terminated and continues. Of course, in this case, it is apparent that the controller 250 may generate the m + 1th event regardless of the termination of the mth synchronization.

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 communication unit 210 receives the m-th synchronization command from the p-th web hard server 130-p, it may output it to the synchronization processor 240, and the synchronization processor 240 may input the m-th synchronization command. According to the m-1 synchronization to generate the m-th synchronization information for the updated data. That is, when the m-th synchronization command is input, the synchronization processing unit 240 may perform the newly updated data (ie, data deleted and / or uploaded data after the m-1 synchronization is completed) after the m-1 synchronization is completed. The m-th synchronization information may be generated and transmitted to the communication unit 210, and the communication unit 210 may transmit the m-th synchronization information to the p-th web hard server 130-p.

In addition, the synchronization processor 240 reads the m-th transmission target data, which is newly uploaded data, from the data storage unit 230 after the m-th synchronization is completed according to the m-th synchronization information, and then the communication unit 210. The communication unit 210 may transmit the input m-th transmission target data to the p-th web hard server 130 -p.

That is, the controller 250 generates information about the updated data and / or information about the updated time whenever the data is updated in the data storage 230, and connects the storage space (for example, the data storage unit). 230, etc.), whereby the synchronization processor 240 may generate information (ie, m-th synchronization information) about data newly updated after the m-th synchronization is completed.

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 controller 250. This is because the m-th synchronization command may be generated in the web hard server where the m-th transmission target data is stored.

For example, the control unit 250 may generate and store information on the time at which the m-1 synchronization ends when the m-th transmission target data is transmitted to the p-th web hard server 130 -p, Thereafter, when the preset time elapses, the m-th synchronization command may be generated and transmitted to the synchronization processor 240. Therefore, the synchronization processor 240 may generate the m-th synchronization information according to the m-th synchronization command generated by the controller 250.

For another example, the controller 250 may generate the m-th synchronization command immediately after data is newly updated after the m-th synchronization is completed. That is, when data stored in the data storage 230 is deleted by the operator or the user terminal 110 or new data is uploaded by the operator or the user terminal 110 to the data storage 230, the controller ( 250 may generate the m-th synchronization command and transmit it to the synchronization processor 240.

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 domain input window 310 in which the domain address of the p-th web hard server 130-p to be synchronized is input, and an operator manipulates the n-th web hard server 130-n. Password input window 320 for inputting a password to be input in order, an operation time input window 330 for inputting a condition for generating an event or a synchronization command, and a sink option input window for inputting a type of data to be synchronized ( 340), the latest sync date display window 350 displaying the time at which the m-1 synchronization has ended, and the sync status display window 360 displaying whether the synchronization is currently being performed are illustrated.

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 domain input window 310. And, the password input window 320 may enter a password for operating the n-th web hard server (130-n), the operation time input window 330 to enter a time condition for the event occurs The type of data to be synchronized may be input to the sync option input window 340.

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 data storage unit 230, only data included in a My folder, a Shared folder, and a Visitor folder may be synchronized.

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 data storage 230. Therefore, if the information about the m th deletion target data does not exist in the m th synchronization information, the second web hard server 130-2 does not have to delete the data stored in the provided storage space. It can be obvious that it can be omitted.

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)

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, M is a natural number web server. The method of claim 1, And the synchronization processor deletes 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 method of claim 1, And a controller configured to store the m-th transmission target data in the data storage unit and generate an m + 1th event when a predetermined time elapses. A synchronization processor for generating m-th synchronization information on data updated after m-th synchronization according to an m-th synchronization command, and detecting m-th transmission target data corresponding to the m-th synchronization information; And And a communication unit configured to transmit the m-th synchronization information and the m-th transmission target data to a storage device connected through a network. M is a natural number web server. The method of claim 4, wherein And the m-th synchronization command is received from the storage device. The method of claim 4, wherein And a control unit for generating the m-th synchronization command when the m-th transmission target data is transmitted to the storage device and a preset time elapses. In the method of synchronizing data with another storage device in the web hard server, Transmitting an m-th synchronization command to a storage device connected through a network when the m-th event occurs; Receiving m-th transmission target data from the storage device in response to the m-th synchronization command; And And storing the m-th transmission target data in a storage space provided with the same. M is a natural number. The method of claim 7, wherein And deleting m-th deletion target data from the storage space according to the m-th synchronization information received from the storage device in response to the m-th synchronization command. The method of claim 7, wherein And generating the m + 1th event when the mth transmission target data is stored in the storage space and a preset time elapses. In the method of synchronizing data with another storage device in the web hard server, Generating m-th synchronization information on the data updated after the m-th synchronization according to the m-th synchronization command; Detecting m-th transmission target data corresponding to the m-th synchronization information; And And transmitting the m-th synchronization information and the m-th transmission target data to a storage device connected through a network. M is a natural number. The method of claim 10, Generating the m-th synchronization information, Receiving the m-th synchronization command from the storage device. The method of claim 10, And generating an m + 1th synchronization command when the mth transmission target data is transmitted to the storage device and a preset time elapses. 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.
KR1020090043336A 2009-05-19 2009-05-19 Web hard server and data synchronization method thereof KR20100124377A (en)

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)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20170046901A (en) * 2015-10-22 2017-05-04 삼성에스디에스 주식회사 Method for synchronizing of dictionary of deduplication

Cited By (1)

* Cited by examiner, † Cited by third party
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