KR100935831B1 - A method for a data synchronizing based on a data structure which has multiple event identifier and the Data back up solution uses the method - Google Patents

Abstract

The present invention relates to a data synchronization method for performing intelligent data backup behavior between a server and a PC, and a data backup solution using the same. The data backup solution according to the data synchronization method of the present invention, unlike the conventional backup solution storage method, the data stored in the server acts as the original data and the data stored in the PC acts as the work data automatically and automatically Manage.

The present invention performs data synchronization between a server and each PC file using CDP (Continuous Data Protection) technology based on an Event Condition Action (ECA) model. Is stored as a data structure having a generation identifier of and at least two change identifiers generated and changed after the generation time of the generation identifier.

In addition, a data synchronization method of selecting data to be deleted based on any one of the identifiers and synchronizing the storage object, the call object or the delivery object data based on the other identifier is applied.

In the ECA model used in the present invention, a condition for maintaining synchronization between the server and the PC is first defined as an event of a file change in the user's PC. The backup list generated by the event is backed up to the server according to the time defined by the system or user by ActiveML which is a data structure of XML format newly defined in the present invention. The data stored on the server can be restored at any time you want.

The system implementing the present invention is different from the one-way backup method in which a PC manually uploads a file to maintain a backup copy on a server in the existing personal backup solution, and automatically compares files stored between the server and the PC. It provides a bi-directional, active backup method that uploads and downloads to maintain synchronization in real time. In addition, various complicated backup requests that can occur in a complex personal computing environment where multiple files are simultaneously operated on multiple PCs can be performed while deleting files and creating a file after changing a file name. In other words, convenient backup data synchronization is possible, such as backing up a specific work status of a PC not synchronized at a specific point of time to a server, or automatically integrating server data at a specific time and work data of a PC not synchronized with the server. Do.

Data, synchronization, backup, identifier, synchronization, hash fuction, time stamp, XML, ECA, event-driven

Description

A method for a data synchronizing based on a data structure which has multiple event identifier and the Data back up solution uses the method}

The present invention relates to a data synchronization and automatic data backup technology for synchronizing data in a networked personal computing environment and performing database management tasks such as sorting, storing, deleting, and calling.

end. Status of the technical field to which the present invention belongs.

As the personal computing environment is networked, the amount of data to be preserved is increasing rapidly. As a result, the need for backup to securely preserve not only corporate data but also personal data is increasing. According to a 2002 IDC survey, 75 percent of a company's critical data is stored on a personal PC, not on a server. In addition, according to the 2004 Gartner report, about 30% of PC disks are important data for individuals, and only 30% of the data are processed and stored in server areas such as ERP / groupware / KMS / EDMS.

Accordingly, the backup target is spreading to the personal data backup method using the external disk and web-based personal backup solution (for example, commercial program package) to safely manage personal data in the existing system management method.

The cost of loss of backup of personal PC data has been around $ 18 billion in recent years. Insurance agency analysis shows that the types of loss of personal data are user error (29%), virus (6%), hardware error (40%), software error (13%), and theft (13%). One disk failure occurs every 1,000 PCs a week, with an estimated damage of $ 4,016 per incident.

Among the above losses, losses due to system failures and viruses (59%) can be improved by backup / recovery software, and losses due to theft and damage (13%) can be improved by distributed / dual backup methods. . In other words, the problem can be solved with a dedicated backup solution for personal data.

However, personal backup solutions have problems with external disk management, manual and cumbersome upload / download process, usage cost, and security of important data on third party server. In particular, it is difficult for existing systems to maintain the latest backup automatically or simply keep the data synchronized among files distributed among multiple PCs with simple operation.

For this reason, most personal backup solutions are still used to store data as a preventive measure in case of a failure.

Dacom's web hard, KTH's web backup service, which is widely used for personal data backup in Korea, is a method of paying a monthly fee and renting a certain space on a web server, that is, ASP service. However, these services require a manual upload / download process of the user and do not automatically synchronize duplicated data on multiple PCs. Recently, Korea's Clarus has released a product that supports real-time backup and encryption, but this also utilizes the real-time monitoring technology for the efficiency of the backup function. Does not support in-sync methods.

Table 1 compares the technical levels of Korea's leading personal backup products.

Comparison of Technology Levels of Korea's Leading Personal Backup Products       Type Function Dacom KTH Clarus Web hard Web backup Intellito Pro Service delivery method Web based ASP service Web based ASP service PC-based solution Backup source Personal PC data Personal PC data Personal PC data Backup target DACOM's web hard server KTH's Backup Server User backup server Backup method Instant backup cycle / hourly scheduled backup Multi-scheduled backup by initial full backup / immediate backup task First full backup / immediate backup hourly multiple scheduling backup Real time backup Not supported Not supported Real time backup available Insufficient change file backup Incremental back up Back up only changed files Delta backup Back up only changed files With changed files   Search only folders and back up Encryption / Compression Not supported Block-by-block compression / encryption Password cannot be set for each file Self-compression / Encryption method File-specific password cannot be set Backup folder / file version management Version control by file last modified date Hourly backup version management Hourly backup version management Backup sync Not supported Not supported Not supported Recovery method Web-based recovery Recoverable by web-based recovery version Solution-based recovery can be recovered by recovery version

On the other hand, foreign personal backup products, like most domestic products, are mostly ASP services that rent a web server space for a certain cost. Recently, products using Continuos Data Protection (CDP) technologies such as Symantec's "Backup Exe 10d" and IBM's "Tivoli CDP for Files" have been released. However, the operating system and environment are limited. In addition, the US Carbonite Backup or Data Deposit Box supports CDP technology to provide real-time backup function, but is mainly provided for ASP type backup service for data loss. In addition, existing foreign products do not provide an automatic management function of personal data using an event-driven synchronization protocol operated by a PC server developed in the present invention to be described below. Table 2 compares the technical levels of the leading international personal backup products.

Comparison of Technology Levels of Leading International Personal Backup Products      Type Function IRON Mountain Inc. Acpana Business Systems Inc. Carbonite Inc. Data Protector Data deposit box Carbonite backup Service delivery method Web based ASP service Web based ASP service PC-based ASP Service Backup source Personal PC data Personal PC data Personal PC data Backup target Backup server Data Deposit Box Backup Server Carbonite Backup Server Backup method First full backup Immediate backup Scheduled backup Immediate backup of the first full backup First full backup Back up every 24 hours for changed files Real time backup Not supported Backup by background backup process based on time interval   Processor driven About new file Backup at Agent restart Incremental Backup Delta backup Back up only files that have changed based on the most recent backup Based on recent backups   Back up only changed files Based on recent backups   Back up only changed files Encryption / Compression No encryption key setting for transmission after block unit compression Use password for web access Backup filegroup sharing Unable to set password for each transmission file after pre-encryption Backup folder / file version management Hourly Version Control Hourly Version Control Hourly Version Control Backup sync Not supported Not supported Not supported Recovery method Recoverable only with version-specific recoverable solution Recoverable by version-recoverable web service Recoverable only through solution

I. Introduction of data processing related technology on which the present invention is based.

Data synchronization is a technique for matching the content of specific data distributed over two or more logical devices on a network. Backup is a concept of batch copying data existing in the raw device to the destination device, but synchronization is a concept of matching data between the raw device and the target device according to the synchronization mode. In other words, synchronization is a technology that allows data to be consistently applied among multiple devices by applying the same change to data of a target device when a change such as input, modification, or deletion occurs in a raw device.

In data synchronization, data synchronization is performed at specific time intervals or at specific time intervals, and when data changes on one side, data is changed in real time.

Recently, as the wireless Internet service is activated, a problem for synchronizing data between a wireless terminal and data with a PC or a server has emerged as an issue. Accordingly, the industry has widely used SyncML (Synchronization Markup Language) as a synchronization standard protocol to ensure interoperability among various heterogeneous devices.

SyncML is a synchronization standard protocol created by the SyncML Consortium to address data interoperability in heterogeneous environments. SyncML can be applied not only to data synchronization between mobile and PC, but also for all distributed data synchronization tasks, including data synchronization between PC and PC, PC and mainframe.

SyncML consists of a SyncML representation protocol (XML representation) containing information necessary for data synchronization, a synchronization protocol (MessageML Protocol) required for message handling, and a transport binding for sending and receiving messages on the network. 1 is a diagram representing a framework of SyncML.

Continuos Data Protection (CDP) technology provides fast recovery times and flexible recovery points on a block or file basis by continuously storing backup copies of file changes such as file creation and modification. CDP technology is expected to evolve into a new technology that can easily back up data by event and manage data conveniently without manual operation of administrator or user. In Korea, CDP technology is still in its infancy, and in foreign countries, it has been activated since 2006 through CDP products such as Symantec's Backup Eject 10d and IBM's Tivoli CDP for Files.

Synchronization solution is a technology that connects personal information such as e-mail, address book, phone number, etc. distributed in various terminals such as PC, PDA, and mobile phone by wire and wireless. Overseas, the International Synchronization Technology Association, which is formed by world-class companies like IBM, Motorola and Nokia, is conducting certification tests for synchronization solution technology. In Korea, companies such as Infobank, Neosteps and iSoft are actively researching for the development of wired / wireless synchronization solution products between wireless terminals and PCs. The technology for automatically synchronizing personal data distributed in PCs, notebooks, and servers developed in the present invention is still in its infancy at home and abroad.

The model referred to for applying the data synchronization method of the present invention is an event occurrence conditional action model through real-time monitoring of data, that is, an active database model based on the event condition action (ECA) technique. An active database model is a database model that automatically performs a defined action when a condition for an event is satisfied. A typical database manipulates data by the user using an application or directly accessing the database. However, in an active database, it is a database model that automatically performs appropriate actions according to the conditions defined in the rules without user intervention. The appropriate behavior is, for example, when a predefined condition such as creation / modification / storage / movement occurs in a specific file (data), an identifier according to a specific rule is generated and stored in a predetermined database area. Say 2A and 2B are diagrams illustrating differences in operational concepts between a general database and an active database.

Recently, the event-driven service technology that detects and analyzes events occurring in real time using the ECA model (file real-time monitoring) and responds to them is used in various fields. . This technology can provide rapid response by monitoring and analyzing various information generated in real time in the business process.

All. Published prior art disclosed in major patent publications.

As a technique for backing up data through real-time monitoring of a file, there is a data backup method disclosed in Japanese Patent Laid-Open No. 2002-0065976. This is a technology for rapidly backing up only files with identifiers when performing a backup operation of a file after recording an identifier in a change file through real-time monitoring. However, there is a feature in that an identifier once recorded is deleted for the next backup. It is not a method of synchronizing data using identifiers according to various situations while the identifiers remain as is.

There is a data synchronization method disclosed in Korean Patent Laid-Open No. 2004-0056639 as a publicly disclosed technique for resolving data synchronization and update conflict between a client and a server. It adopts log sequence number (LSN) and TS (time stamp) as change identifier, and retrieves the change history of specific client by log sequence number after the time stamp according to time stamp and blocks it from server. It is characterized by detecting and solving errors in the synchronization process that impairs the consistency of data as a technique for preventing write conflicts or operation conflicts during real-time use of the data. However, as in the present invention, various inconsistent data are not changed during data synchronization. The change identifier is not used to be able to survive.

Another data synchronization related disclosure technology looks at the data synchronization method disclosed in Japanese Patent Laid-Open No. 2005-0089551. For data synchronization between the server and client, this data is not synchronized by deleting the contents of the Synchronization time information (corresponding to the timestamp as an identifier) field when a particular data has been changed or deleted after a recent synchronization or newly created. It is characteristic in that it can be seen that the changes are not.

However, even in this case, the technical concept of the present invention is different from that of the present invention, in which an identifier as synchronization information remains intact and takes a correspondence through separate generation or the like even for data changed in duplicate from two or more clients. Do not.

An object of the present invention is to implement a method and solution for automatically managing personal data in a PC-class server using CDP (Continuous Data Protection) technology based on the Event-Condition-Action (ECA) model.

As described in the background art, conventional technologies for accessing data synchronization as a personal backup solution have a lack of flexibility in operating the system, which is compared with the present invention as follows.

Challenge-(1). Traditional backup method

① Operation method: Time based backup or change based backup

② Backup method: Overwrite change information every time backup or file change based on hourly backup schedule strategy (incompatible with each other)

③ Backup copy: Save only the copy by version or the last changed copy according to the time when backup was performed.

④ Restoration method: It is possible to recover only to the various points of time when the backup is performed or only to the last changed state.

⑤ Advantages and disadvantages: In case of time-based backup, there is a risk of data loss between a specific backup point and failure point. In the case of change-based backup, data recovery is impossible.

Challenge-(2). Various situations in a real personal computing environment

The biggest difference between the personal computing environment and the working environment between the general server and the client is that a large number of files can be processed out of order, and asynchronously on a specific PC due to the user's intentional needs or unintended mistakes. There may be a process of changing a number of individual files in a state.

In this case, both the backup data in the individual files backed up to the server by synchronizing with the change data in the individual files on the specific PC worked unsynchronized can be important data for the user.

In order to understand this easily,

For example, a user backs up files A, B, and C on a company's PC 1 and then backs up to the server. After working at home, working on D, E, and F files without syncing with the server on his personal PC 2, he suddenly comes up with an idea. When modifying A file, it's easy to imagine the process of creating a specific report using a combination of multiple picture editors, slide editors, and word / excel editors between company and home.

At this time, if the A file worked on PC 1 contains the contents that are difficult to discard,

In addition, there may be conditions for creating and changing various files independently, such as when the C file backed up to the server is affected by the result of A file worked on PC 2.

In all of these situations, it is difficult for a user to manually identify and modify files manually, or to create a file that is difficult to modify, and to create a new file name. In particular, it is possible to perform collective point-in-time recovery or batch overwriting of changed files. Various situations arise that are difficult to solve by themselves.

This is because the relationship between PC and backup server in personal computing environment is different from that of general client and server (such as essential dependency in the process).

The main problem of the present invention is to solve the above situation flexibly and automatically without additional effort of the user. In contrast with the existing backup method introduced in the above task- (1).

Challenge-(3). The problem differentiated from the existing backup method pursued by the present invention.

① Operation Method: Intelligent backup combining change base and time base

② Backup method: There is no backup schedule and automatic backup when file is changed

③ Backup copy: Save copy for each version according to every change of file, and additionally create the file in case of duplicate change

④ Restoration method: Restoration to all previous state changed

⑤ Advantages and disadvantages: If necessary, data can be accessed at the desired time and as the result of PC work.

Can be presented as above.

In order to achieve the object of the invention as described above, the present invention is first completed using the following main problem solving means.

First, a data structure type (named ActiveML in the present invention) having at least one occurrence identifier and at least one change identifier generated and changed after the generation time of the occurrence identifier is defined.

Next, the data to be deleted is classified and deleted based on any one or more of the identifiers of the identifiers of the data structure, and the data to be synchronized with the storage object, the call object or the transfer object data based on the other identifier. Create a synchronization method.

Finally, a logical database is constructed in the form of the data structure and a data backup processing module using a data synchronization processing module using a specific expression protocol among SyncML expression protocols, that is, a data synchronization engine driven by the data synchronization method, is implemented.

The technologies secured for the above solutions are largely divided into four types. First, in order to implement the CDP method, which has been recognized as a new technology for data protection since 2006, the company has secured the technology to continuously manage personal data automatically using the ECA method used in the active database model. In addition, we secured the technology to synchronize files distributed on multiple PCs and server files in real time, and newly defined ActiveML, an XML data structure that enables this. In addition, it secured its own encryption technology to protect personal data stored in the server even in the case of network / server hacking. Finally, we have secured a full recovery technique and a partial recovery technique to recover data to all changed points supported by the CDP method.

The technology developed in the present invention utilizing the above technologies is a low cost-high efficiency platform independent technology that can be operated by open source software such as Linux and Java in a PC-class server.

In the present invention in which the above-mentioned solutions are used, it supports automatic synchronization between data distributed to several PCs based on the original data stored in the server.

For example, in the existing backup solution, the data stored in the PC becomes the original data, and the data stored in the backup server acts as a copy. On the other hand, in the system implementing the present invention, the data stored in the server is the original data, the data stored in the PC serves as the work data.

The solution implementing the present invention automatically uploads a file to the server disk when an event such as file creation or modification occurs on the user's PC. And when your PC or laptop is connected to the Internet, you can automatically download the latest data stored on the server disk and continue working. After work, the changed files are uploaded to the server in real time and synchronized with the data stored on the server disk, so you can always manage the latest files effectively.

First of all, it is different from the existing one-way backup method, and it is possible to prevent various important data from being lost by synchronizing effectively after various additions or deletions by time and location. By encrypting files on your PC and uploading them to the server disk, you can safely manage your data even on server or network hacking.

The system implementing the present invention was developed as a platform-independent solution using open software such as Java and Linux on a PC-class server. The solution embodying the present invention is expected to contribute to revitalization of knowledge-based society as a solution for effective knowledge management centered on individuals.

The application field of the system implementing the present invention is in the field of business data management system, UCC, reports, plans, experimental data, etc. to systematically manage business knowledge documents by using a low cost-high efficiency PC server in small and medium-sized enterprises, research institutes, etc. It is expected to be utilized in various fields such as personal data management system field for systematic management of the same personal knowledge.

In order to more specifically represent the main technical features of the present invention will be described in more detail below with reference to an example of the present invention included in the drawings.

However, in the embodiment of the invention or the specific example described below, the components including specific terms and their specific coupling structures limit the idea that is inherent in the technical features of the present invention. It is not known in advance.

Content-1. Event rule definitions based on ECA models

An event occurs when a user works on a system or file on a PC. The event defined in the present invention is largely divided into an event which can be automatically detected from a system point of view and an event that can be arbitrarily designated by a user. Tasks such as file manipulation or operating system startup / shutdown are defined as events from the system perspective, and tasks such as backup scheduling are defined as user-defined events. Table 3 is an event definition defined in the present invention.

Event definitions Event classification Event definitions System events file  Create, update, delete, rename files operating system  Operating system startup, shutdown time  Idle time Custom events  Scheduling definition, automatic backup timer

In the present invention, processing conditions are specifically defined for each event by using an immediate decision, a delay decision, and a separation decision technique used when evaluating conditions of an ECA model.

Immediate judgment is a technique that checks a condition as soon as an event occurs and performs automatic backup when the condition is satisfied. Immediate determination is used when a system event developed in the present invention occurs. Table 4 defines the events and conditions corresponding to the immediate decision technique.

Define instant verdict conditions event Condition Definition  File events  -A file event occurs and there is no user specified automatic backup timer  Operating system events  -When an operating system event occurs  Time events  -If the specified idle time is satisfied

Delayed determination is a technique that waits until an event occurs and a certain condition is satisfied, and then checks the condition and performs automatic backup when the condition is satisfied. The delay determination is applicable to the event and condition shown in Table 5.

Delay judgment condition definition event Condition Definition File events  -Delay until user specified automatic backup timer time is satisfied-Delay until user specified scheduling time for periodic backup

Branch decision is a technique that checks a condition and performs automatic backup when the condition is true when the user wants to perform 'manual backup manually' regardless of the event.

An action defines an action to be executed when conditions defined for each event are satisfied. In the system implementing the present invention, as soon as the conditions defined for each event are satisfied, actions are executed in the order of 'synchronization', 'encryption / decryption of files', and 'upload / download'.

Content-2. SyncML representation protocol underlying ActiveML, the present data structure

The SyncML Representation Protocol is a well-defined XML document for defining message structures for data synchronization. SyncML messages are described with information such as data handling commands, device information, synchronization data, and other metadata. The following XML statement is a simple example of the SyncML representation protocol specification.

<SyncML xmlns = 'syncml: syncml1.0'>

    <SyncHdr>

        <VerDTD> 1.0 </ VerDTD>

        <Source>

            <LocURI> http://www.datasync.org/servlet/syncit </ LocURI>

        </ Source>

    </ SyncHdr>

    <SyncBody>

        <Get>

            <CmdID> 0363 </ CmdID>

        </ Get>

    </ SyncBody>

</ SyncML>

The SyncML synchronization protocol provides seven synchronization types as a standard for information, authentication, and synchronization types used for internal operations. Table 6 shows the synchronization types proposed by the SyncML synchronization protocol. Here, a database managing file information of a server is called a target database, and a database managing client file information is called a source database.

Types of synchronization provided by the SyncML synchronization protocol Synchronization type Technology Two-way sync -Client and server exchange information about change data   Common sync type The client sends the changed information first Slow sync Two-way sync, where all items are compared against each other in field-to-field fields. Actually, the client sends all data in the database to the server. One-way sync from client only -Client sends change information to server, but server does not send change information to client Refresh sync from client only The client sends data from the source database to the server, and the server replaces the server's target database with the received data. One-way sync from server only The client receives the target database data from the server but does not send the client's source database data to the server. Refresh sync from server only The server sends the target database data to the client, and the client replaces the client's source database with the received data. Server Alerted sync The server notifies the client of the start of the specified type of synchronization

In the present invention, the synchronization data is developed based on two-way sync, one-way sync from client only, and one-way sync from server only types among the synchronization types of the SyncML synchronization protocol.

Content-3. Data synchronization technology of the present invention

Content-3- (1). ActiveML definition

In the present invention, a data structure called ActiveML (Active sync Markup Language) is newly defined by referring to the expression protocol of SyncML for processing synchronization data between a user PC and a server. ActiveML is a data structure defined to transfer synchronization information about change files between PC and server using synchronization module. ActiveML consists of authentication information about users and sessions, backup and recovery device information, synchronization methods, synchronization commands, and information about synchronization files. FIG. 3 is a schema structure diagram of ActiveML for defining synchronization data, and Table 7 defines elements and attributes of ActiveML including the structure of FIG. 3.

ActiveML element definition Element name Explanation  ActiveML Root Element in ActiveML Schema  ActiveHeader Complex element representing user information, synchronization date and method  ActiveBody Complex element representing information about the synchronization file and file-specific commands  SessionID Element representing user session key value for session persistence  UserId An element representing a user ID  MacAddress An element representing the Mac Address of the user device  TargetServer Element representing the domain or IP address of the server of the present invention  Currentdate Element representing time (year / month / day hour: minute: second) that requested synchronization  SyncMethod Elements representing the kind of synchronization technique (one-way sync from server, one-way sync from client, two-way sync)  SyncData Complex type element representing information about n files requested for synchronization  Final An element representing the end of the synchronization data  File Complex element representing information about each file that requested synchronization Command (CM) Elements representing commands for each file (new creation: 100, recovery: 200, file rename / file modification: 300, deletion: 400, etc.) Global File Id (GF) Element representing a unique hash value for each file that will be used to identify the same file distributed across multiple PCs when synchronizing multiple PCs Local File Id (LF) Element representing unique hash value for each PC file  Serverdir An element representing the physical path where the file is actually stored on the server  ServerFileName Element representing the file name actually stored on the server-a value consisting of GlobalFileId + MacAddress + LastModifyDate FileName An element representing the name of the file that requested synchronization LastModifyDate (LM) An element representing the creation date or last modified date (year / month / date hour: minute: second) of the file that requested synchronization. ServerModifyDate (SM) The last time the file was stored on the server, synced with the sync timestamp ( Element representing year / month / day hour: minute: second)  Filesize Element representing file size (in bytes) requested for synchronization  EncryptStatus An element representing encryption  EncryptType An element representing the encryption algorithm used to encrypt the file

In Table 7, the elements shown in bold correspond to the identifiers that perform the core functions of the present invention.

An identifier is defined, created, modified, and stored to uniquely distinguish the information for processing. The identifier refers to a name that can uniquely identify and distinguish an object. Expressed in element form. Typical identifiers include URL, ISBN, and IP address.

In Table 7, the GlobalFileId (GF) and LocalFileId (LF) occurrence identifiers may be a combination of 32-character pseudo-random characters + numeric strings using a hash function. As described below, LocalFileId may be defined as a local occurrence identifier, and GlobalFileId is global. It can be defined as an occurrence identifier.

Command (CM) may be event information such as file creation / change, and may be defined as an event change identifier. LastModifyDate (LM) and ServerModifyDate (SM) may be time information (year, month, date, minute, second) using a timestamp. As described below, LastModifyDate may be defined as a time change identifier, and ServerModifyDate may be defined as a synchronization change identifier. .

The occurrence identifier is generated once when the data (file) is created for the first time, and it can be named as an identifier because it is set not to change until the data is deleted.

Similarly, the change identifier is generated when the data is first saved / uploaded, and the change identifier is set to have a changed value whenever the data (file) is stored after modification and uploaded to the server.

For example, when a specific file is first generated, the file version DB structure as shown in Table 8 may be stored in the ActiveML structure of the specific file.

 File Version DB Structure Attribute name type Explanation Local File Id (LF) char (32 characters) -Identifier to distinguish uniqueness of each PC file-Change file name to hash value-Example: 04E237984C889A2140F6A4463ADCD9A5 Global File Id (GF) char (32 characters) -Identifier to identify the same file distributed on multiple PCs-Used by replacing the file name with a hash value-Example: 2319941095FC3CEF517030AE846A3653 Folder ID char (32 characters) -Identifier to identify the uniqueness of the folder-Change the folder name to a hash value-Example: 5232FC3CEF517030A1232345B8978753 Filename char -Filename-eg: \ backup \ file \ intro_xml.camproj LastModifyDate (LM) char -Date of last modification of the file-Date of creation of the file in case of a new file-Date of last modification of the file in the case of a new file-Example: 2008/03/27 18:48:30 ServerModifyDate (SM) char -Date automatically backed up by condition-Ex: 2008/03/27 18:48:40 File size integer -The actual size of the file, in bytes-eg 47616 File encryption integer -Choose whether to encrypt files Encryption algorithm integer -File encryption algorithm selection-e.g. 1-RC4, 2-RC5, 3-DES, 4-AES Command (CM) integer -Event command per file detected by file monitoring tool-100 (create), 300 (modify), 400 (delete), 500 (done), etc.

According to Table 8, the identifiers of Local File Id (LF) and Global File Id (GF) are suitable for identifiers having a certain character length for fast uniqueness / identity comparison. For example, a hash function is used. The string of 32 characters (including numbers) can be used.

Likewise, according to Table 8, the command (CM) may use a numeric string to mechanically express the file-specific event detected by the file monitoring tool. LastModifyDate (LM) and ServerModifyDate (SM) may use numeric strings having time information of year , month , date , minute , and second in order to make it easier to determine before and after the time of storing and backing up files in the synchronization processing module.

Content-3- (2). ActiveML-based synchronized XML instance.

In order to exchange synchronization information between PC and server through data synchronization engine, ActiveML-based synchronization information for new, changed and deleted files is required. The ActiveML generation module creates an ActiveML-based synchronization XML instance using the file change information (Backup Resource) created by the event rule processing engine. The following is an example of an ActiveML-based synchronization XML instance (modification / deletion / download / new creation definition) applied to the present invention.

<? xml version = '1.0' encoding = 'UTF-8'?>

 <ActiveML xmlns: xsi = 'http: //www.w3.org/2001/XMLSchema-instance'

            xsi: noNamespaceSchemaLocation = 'activeml.xsd'>

 <ActiveHeader>

  <SessionID> 7D5187A7344F5609314EDD2A8CE2079B.tomcat </ SessionID>

  <UserId> ihjun </ UserId>

  <MacAddress> 7a: 79: 05: c4: cd: 64 </ MacAddress>

  <TargetServer> activeDisk.hibrain.net </ TargetServer>

  <CurrentDate> 2008/05/2714: 31: 20 </ CurrentDate>

  <SyncMethod> two-way sync </ SyncMethod>

  </ ActiveHeader>

 <ActiveBody>

 <SyncData>

 <File>

    <!-If the file has been modified->

    <Command> 300 </ Command>

    <GlobalFileId> 0B6A15BC715F964DD8D3CA0FCAA5C4AB </ GlobalFileId>

    <LocalFileId> 8C65781D2EBC3C2FB493CB25D3F769EE </ LocalFileId>

 <ServerDir> / home4 / activedisk / disk0 </ ServerDir>

 <ServerFileName> 0B6A15BC715F964DD8D3CA0FCAA5C4AB7a7905c4cd64 2008: 05: 2714: 31: 13 </ ServerFileName>

    <FileName> XGJhY2t1cGZvbGRlclzsoITsnbjtlZjsl4XrrLTrs7Tqs6AyMDA3MDgxMy 50eHQ = </ FileName>

    <LastModifyDate> 2008/05/2714: 31: 13 </ LastModifyDate>

    <ServerModifyDate> 2008/05/2714: 05: 26 </ ServerModifyDate>

    <FileSize> 261 </ FileSize>

    <EncryptStatus> 0 </ EncryptStatus>

    <EncryptType> 0 </ EncryptType>

  </ File>

  <File>

    <!-If file is deleted->

    <Command> 400 </ Command>

    <GlobalFileId> 3D0595959EDFF7281EF5AEB9040BD63E </ GlobalFileId>

    <LocalFileId> 68863DD725272BD76A4981D2AB760918 </ LocalFileId>

    <ServerDir> / home4 / activedisk / disk0 </ ServerDir>

    <ServerFileName> 3D0595959EDFF7281EF5AEB9040BD63E7a7905c4cd642008: 05: 2714: 31: 20 </ ServerFileName>

    <FileName> XGJhY2t1cGZvbGRlclzsoITsnbjtlZjsl4XrrLTrs7Tqs6AyMDA3MTAwMS50e HQ = </ FileName>

    <LastModifyDate> 2008/05/2714: 31: 20 </ LastModifyDate>

    <ServerModifyDate> 2008/05/2714: 03: 40 </ ServerModifyDate>

    <FileSize> 318 </ FileSize>

    <EncryptStatus> 0 </ EncryptStatus>

    <EncryptType> 0 </ EncryptType>

  </ File>

  <File>

    <!-The file has been modified on another PC and the download

        If necessary->

    <Command> 200 </ Command>

    <GlobalFileId> E09CD8103762128446B8BF001B0875A9 </ GlobalFileId>

    <LocalFileId />

    <ServerDir> / home4 / activedisk / disk0 </ ServerDir>

<ServerFileName> E09CD8103762128446B8BF001B0875A9001d926c015e2008: 03: 1717: 52: 02 </ ServerFileName>

    <FileName> XGJhY2t1cGZvbGRlclxwYy50eHQ = </ FileName>

    <LastModifyDate> 2008/03/1717: 52: 02 </ LastModifyDate>

    <ServerModifyDate> 2008/05/2714: 04: 13 </ ServerModifyDate>

    <FileSize> 79 </ FileSize>

    <EncryptStatus> 1 </ EncryptStatus>

    <EncryptType> 1 </ EncryptType>

  </ File>

 <File>

    <!-When a file is newly created->

    <Command> 100 </ Command>

    <GlobalFileId> 2B66B314783B1CCDEB32D39CD348A43F </ GlobalFileId>

    <LocalFileId> 49841FFBE76E0E29C8FD141ADCF110BA </ LocalFileId>

    <ServerDir> / home4 / activedisk / disk0 </ ServerDir>

    <ServerFileName> 2B66B314783B1CCDEB32D39CD348A43F7a7905c4cd642007: 10: 0810: 26: 08 </ ServerFileName>

    <FileName> XGJhY2t1cGZvbGRlclzsoITsnbjtlZjsl4XrrLTrs7Tqs6AyMDA3MTAwOC50 eHQ = </ FileName>

    <LastModifyDate> 2007/10/0810: 26: 08 </ LastModifyDate>

    <ServerModifyDate> 2008/05/2714: 05: 26 </ ServerModifyDate>

    <FileSize> 439 </ FileSize>

    <EncryptStatus> 0 </ EncryptStatus>

    <EncryptType> 0 </ EncryptType>

  </ File>

  </ SyncData>

  <Final />

  </ ActiveBody>

</ ActiveML>

Content-3- (3). Synchronization protocol definition using ActiveML

In the present invention, 'One-way sync from client only' and 'One-way sync from server only' types are used for one-way synchronization among seven synchronization types of SyncML synchronization protocol. In addition, we developed a synchronization protocol using the ‘Two-way sync’ type for bidirectional synchronization.

First, one-way sync from client only synchronization method is a synchronization method used when a new automatic solution is installed on a user's PC and then the first automatic backup is performed. Sends the information of all files below the folder designated as backup folder to the server. 4 is a diagram illustrating the concept of a one-way sync from client only synchronization protocol used in the present invention.

Next, the One-way sync from server only synchronization method is used when an existing user installs a client module on a new PC. Transfer all user folders and files already backed up to the server to your PC to stay in sync. 5 is a diagram illustrating the concept of a one-way sync from server only synchronization protocol used in the present invention.

The two-way sync synchronization method is a synchronization method used to exchange synchronization information on changed data between a PC and a server. This is the most common synchronization method after installing the solution. Two-way sync synchronization is used to modify, create, or delete files in a folder or file that you specify.If the version of the file between the PC file and the server is different, the PC sends the sync information to the server for comparison. The server then sends the server synchronization information back to the PC to complete the synchronization. 6 is a diagram illustrating the concept of a two-way sync synchronization protocol used in the present invention.

Content-3- (4). Detect and resolve inconsistency between server and PC data using ActiveML

Using the synchronization protocol introduced in the above contents-3- (3), the synchronization operation in a more complicated situation is introduced.

When synchronization occurs between the server and the PC, the synchronization change identifier (SM) is recorded in the database of the server and the PC. Intentional interruption of synchronization by the user or system and network errors may cause inconsistency in the synchronization change identifier between the server database and the PC database. Therefore, it is necessary to verify by the user whether the file backed up on the server is the most recent file and the file modified on the PC is the most recent file.

For example, on April 29, 2008, a user automatically backed up some modified "final report .hwp" files on computer A at home. The synchronization change identifiers for the final report .hwp file are recorded in the server and PC databases. In the morning of April 30, 2008, the company forcibly stopped the automatic synchronization feature on computer B, and then modified the 'final report.hwp' file stored on computer B. In this case, if the synchronization for automatic backup is performed on computer B again, the synchronization change identifier is inconsistent, so the 'final report.hwp' file backed up to the evening of April 29, 2008 on the server is the latest file. Will need to verify that the 'final report .hwp' file, modified on April 30, 2008, is up-to-date with no synchronization. This does not modify the file that was last backed up from the server on computer B. After downloading it, the file is crashed.

7 is a scenario for detecting inconsistency files between the server and PC data using two identifiers (globally generated identifiers (GFs) and synchronization change identifiers (SMs)) and solving inconsistencies by users. The last synchronization change identifier stored in the PC is compared with the last synchronization change identifier stored in the PC to check whether there is an inconsistency file between the server and the PC file at the time of synchronization. If a mismatch is found, the user verifies whether the PC file is the latest file or the server file is the latest file. When the inconsistency resolution criteria is defined, two-way synchronization is performed using the two-way sync synchronization method described below to synchronize all data between the server and the PC.

Next, a synchronization including additional generation of a file is implemented by using the generation identifiers LF and GF and the change identifiers CM, LM, and SM, which are one of the most complicated forms of the present invention.

First, rearrange the above identifiers,

LocalFileId (Local occurrence identifier-LF)-It is an identifier that is generated when the first event occurs. (Determining whether data exists or not, replacing the file name for each PC) Unique value for each PC file, different values for each PC even if the same file is distributed to multiple PCs. Has-has a unique value that is not modified on both server and PC

GlobalFileId (Global identifier-GF) -Identifier generated at the first event (determination of data existence, file name substitution). Unique value to identify the same file distributed among multiple PCs-Unique value not modified on both server and PC Have

Command (Event Change Identifier-CM)-It is an identifier that is generated like LF at the first event occurrence (data change status judgment).-It expresses the status such as creation, change and deletion through real time monitoring in numerical form. Is modified.

LastModifyDate (Time Change Identifier-LM)-It is an identifier that is generated like LF when an event occurs after the first one. (Date of data change)-Used to determine whether the file has been changed with CM change identifier on PC. The value is modified each time the same event occurs.

ServerModifyDate (Sync Change Identifier-SM) -It is an identifier that is generated when an event is uploaded from the PC to the server (Judged when to synchronize data)-The value on the server and the value on the PC before synchronizing with the server may be different. Then they have the same value.

All five above identifiers are of ECA (Event-condition-Action) type.

The following is a user who works on Personal PC A and synchronizes it with the server (backs up to the server) and then starts up the Personal PC B in another location, but does not synchronize with the server (download from the server). This section describes how identifiers change in the data structures of files stored on the server and personal PC B, assuming changes or creations.

Personal PC A

(Existing data) (Change) (Create)

LF-AFO GF-GFO LF-AFO GF-GFO LF-AF1 GF-GF1

CM-0 LM-0 'SM-1 CM-300 LM-1' SM-1 CM-100 LM-1 'SM-null

-> Backup to Server->

Server storage Personal PC A Sync

(Upload) (Upload) ( Modify SM information of Personal PC A)

LF-AFO GF-GF0 LF-AF1 GF-GF1 (LF-AFO GF-AFO LF-AF1 GF-GF1)

LM-1 'SM-2 LM-1' SM-2 (CM-600 LM-1 ' SM-2 CM-600 LM-1' SM-2 )

-> Work after personal PC B start without syncing->

Personal PC B

(Existing data) (Change) (Create)

LF-BF0 GF-GF0 LF-BF0 GF-GF0 LF-BF2 GF-GF2

CM-0 LM-0 'SM-1 CM-300 LM-2' SM-1 CM-100 LM-2 'SM-null

The subscripts attached to LF and GF are A (PC A), G (used as global value to distinguish the same file when using multiple PCs), B (PC B), and subscripts attached to F (File) subscript are 0,1 , 2 and so on are the only values in the file.

Subscripts attached to LM and SM include 0 = initial time, time from 0 '= 0 to 1 before, 1 = time after 0', 1 '= time from 1 to 2, 2 = time after 1', After 2 '= 2, it is time. Among the subscripts attached to the SM, null represents the information that it has never been backed up.

As described above, in a situation in which the data state of Personal PC A = Server ≠ Personal PC B is caused, various data synchronization operations (A), (B) and (C) may be required from the user as described below.

(A) When a user connects to personal PC B and works without synchronizing with the server, he changes his mind and wants to invalidate the personal PC B work results and synchronize with the server based on the personal PC A work results:

-Since the time information SM-1 of the data structure of the file structure of the personal PC B and the SM-2 identifier information of the server do not match each other, and the SM-2 identifier information of the server is more recent, The changed data in the synchronization data is deleted.

-Synchronize GF-GF0 files from the server after downloading GF-GF0 files with both CM-300 and LM-2 'modified identifier modified after time 2 on personal PC B.

-Upload GF-GF2 file with CM-100 (newly created) and SM-null (not synchronized) newly created after time 2 on personal PC B

-GF reference synchronization from server to personal PC B (download files with GF-GF1 identifiers not present on personal PC B)

-Since the time information of the data structure of the file has time information through the LM-2 'identifier and event occurrence information through the CM identifier, in addition to the time information through the SM-1 identifier, after time 2 (2 ~ 2') Even complex changes such as file creation, deletion and modification can be handled easily, especially creation and change. -It cannot be judged by SM of personal PC B, but it can be judged by CM and LM of personal PC B.

(B) When a user connects to personal PC B and works without synchronizing with the server, and then invalidates the personal PC A work results and synchronizes with the server based on the personal PC B work results:

-The SM-2 identifier information of the server is more recent than the SM-1 of personal PC B, but since the data of personal PC B has changed identifier information changed to LM-2 ', CM-300, the file with the identifier is backed up. Eligible.

-GF standard synchronization from personal PC B to server (upload file with GF-GF0, GF-GF2 identifier)

-GF reference synchronization from server to personal PC B (download files with GF-GF1 identifiers not present on personal PC B)

-Since the time information of the file data structure has time information through CM and LM-2 'identifiers in addition to time information through SM-2 identifiers, file creation and deletion after time 1' (1 '~ 2) This can be easily handled even when there are complex changes such as changes. In particular, creation and change can be easily distinguished. -It can not be judged by SM of server but can be judged by CM and LM of personal PC B.

(C) When a user wants to return to a specific point in time for a personal PC B job while working on his personal PC B:

 -Select a point in time 2 ',

   Among the files being monitored in real time, only the files of the LM before that time are downloaded from the data backed up to the server with the SM before the time, and the files with the LM after that time are deleted from the PC, or the file of the previous LM is named as a new file name. Download to. -It is impossible to distinguish only by SM of server, but it is distinguishable by SM and LM of server.

The following is the state of each file stored in the server and the personal PC B in accordance with the synchronization request of (a) to (b), which is the state of (a) to (c) terminated at the server.

Server-

(No change) (no change) (upload from personal PC B)

LF-AFO GF-GF0 LF-AF1 GF-GF1 LF-BF2 GF-GF2

LM-1 'SM-2 LM-1' SM-2 LM-2 'SM-3

Personal PC B-(a)

(Download) (Download) (Sync info SM change)

LF-BFO GF-GF0 LF-AF1 GF-GF1 LF-BF2 GF-GF2

LM-3 SM-2 LM-3 SM-2 LM-2 'SM-3

-------------------------------------------------- --------------

Server-(me)

(Upload from PC B) (No change) (Upload from PC B)

LF-BFO GF-GF0 LF-AF1 GF-GF1 LF-BF2 GF-GF2

LM-2 'SM-3 LM-1' SM-2 LM-2 'SM-3

Personal PC B-(I)

(Change SM Synchronization Information) (Download) (Change SM Synchronization Information)

LF-BFO GF-GF0 LF-AF1 GF-GF1 LF-BF2 GF-GF2

LM-2 'SM-3 LM-3 SM-2 LM-2' SM-3

The present invention has developed a system for automatically managing personal data in a PC-class server using the data synchronization method as described above. Existing systems are inconvenient by the way of manually backing up and restoring files. However, the system implementing the present invention can manage data quickly and safely by using a method of automatically backing up and restoring a file by an event-driven method. Existing systems also use the files stored on the PC as the original and the files stored on the server as a copy. On the other hand, in the system implementing the present invention, the file stored in the server becomes the latest original file, and the file stored in the personal PC serves as a copy. 8A and 8B are diagrams comparing the operation method of the existing backup solution with the operation method of the present invention.

The system implementing the present invention automatically uploads a file to a server disk when an event such as file creation or modification occurs on a user PC. In addition, when your PC is connected to the Internet, the latest files stored on the server disk can be downloaded to your PC or laptop to automatically keep the synchronization between multiple PCs. After the operation, the changed file is uploaded in real time and synchronized with the data stored on the server disk, so that the user can conveniently manage the latest file without any additional work. 9 is a conceptual diagram of the data backup solution, and FIG. 10 is an operation scenario of the data backup solution.

The data backup solution basically includes an ECA model-based event rule processing module for backing up files in real time as described above, and a synchronization module for resolving inconsistencies among data distributed among multiple user PCs. It consists of a recovery module for recovering files from various points of view, and an encryption module for safe data protection even in the case of network or server hacking.

Example Configuration Event rule processing module based on the ECA model

-Module for defining and processing event rules for uploading and downloading to the server automatically when creating or changing PC data using CDP technology by event-driven method

The event rule processing engine detects operation events on the system and files on the PC and manages information related to changes to the files. The event rule processing engine consists of a file version DB that manages information about files, a file monitoring tool that monitors files and system events, and a file change inspection module that checks whether files have changed. The event rule processing process is to reload the file version DB by loading the existing file version DB and comparing the information of the changed file with the contents of the file version DB in the file change check module when an event is detected by the file monitoring tool. Is done.

FIG. 11 is a conceptual diagram of an ECA model based event rule processing engine mounted in the present embodiment, and FIG. 12 is a flowchart illustrating an operation of the event rule processing engine.

In more detail, the event rule processing engine is largely composed of a file monitoring tool for monitoring files and system events, a file version DB for managing information about changed files, and a file change checking module for checking whether a file has been changed.

File monitoring tools are tools that detect file-based events such as creating, modifying, and copying PC data. In this embodiment, ALFA Corp. Alfa File Monitor was purchased and used.

The file version DB is a file for managing information on newly created or changed files. The file version DB consists of information such as file ID, file name, file size, file creation date, and file last modified date. The information in the file version DB is reconstructed by the file change check module when an operation event occurs for the file. The file version DB is used as information for synchronizing with the server data when the automatic backup action is performed when the event condition defined in the present embodiment is satisfied. Table 9 describes the structure of the file version DB of this embodiment.

File Version DB Structure Attribute name type Explanation Local File ID char (32) -Identifier to distinguish uniqueness of each file-Change file name to hash value-Example: 04E237984C889A2140F6A4463ADCD9A5 Global File ID char (32) -Identifier to identify the same file distributed on multiple PCs-Used by replacing the file name with a hash value-Example: 2319941095FC3CEF517030AE846A3653 Folder ID char (32) -Identifier to identify the uniqueness of the folder-Change the folder name to a hash value-Example: 5232FC3CEF517030A1232345B8978753 Filename char -Filename-eg: \ backup \ file \ intro_xml.camproj File modification date char -Date of last modification of the file-Date of creation of the file in the case of a new file-Date of last modification of the file in the case of a new file-Example: 2008/03/27 18:48:30 File sync date char -Date and time of automatic backup by condition-Ex: 2008/03/27 18:48:40 File size integer -The actual size of the file, in bytes-eg 47616 File encryption integer -Choose whether to encrypt files Encryption algorithm integer -File encryption algorithm selection-e.g. 1-RC4, 2-RC5, 3-DES, 4-AES File command integer -File-specific events and commands detected by file monitoring tools-100 (create), 300 (modify), 400 (delete), 500 (done), etc.

The file change checking module compares the information of the changed file with the information of the file version DB when a file manipulation event occurs and performs a reconstruction operation to construct a new file version DB. First, the file change inspection module examines a log of file manipulation events through a file monitoring tool and stores information of the file in a memory queue. Then, the file version DB is reconfigured to add the information of the memory queue if there is a change by comparing the information of the existing file version DB and the memory queue.

FIG. 13 is a UML representation of a class design diagram for the event rule processing engine. The event rule processing engine detects an event on a file (CFileMonitoring), checks the information of a file version DB (CFileVersionCheck), compares the information on the file where the event occurred, and rebuilds (CBackupResource) a new file version DB. It consists of.

Example Configuration 2. Synchronization module between server data and multiple PC data

Processing module for automatically synchronizing server data and data stored in multiple PCs

-One-way sync from client only: Synchronize when data is changed from PC to server

-One-way sync from server only: Synchronize when the server changes data to PC

Two-way sync between server and client: General form of synchronization for exchanging data between PC and server.

-If the version of the data between the PC data and the data stored in the server is different, the processing module for detecting the discrepancy by the user to select the standard

-Processing module that resolves inconsistency by synchronizing data between server and PC by two-way sync synchronization method

In this embodiment, a data synchronization engine for automatically synchronizing server data and data stored in a plurality of PCs has been developed. Existing backup solution is inconvenient because users manually upload PC file to keep backup copy on server for synchronization between multiple PCs, and then directly download necessary files from server from other PCs. However, in the present invention, by generating the synchronization data for the files stored in the server and the PC, it is possible to configure information about the file that needs to be backed up and the file that needs to be restored. And, by automatically backing up and restoring files based on synchronization information, it is possible to automatically maintain consistency among files distributed among multiple PCs. 14 is a conceptual diagram for data synchronization between a server disk and a PC according to the present embodiment.

The synchronization engine generates an ActiveML generation module for generating synchronization information, an ActiveML transmission module for transmitting synchronization information, and a list of files to be uploaded or down by analyzing the synchronization information of the server to compare the synchronization information between a user PC file and a server file. It consists of an ActiveML analysis module.

15 is a UML representation of a class design diagram for the synchronization engine. When synchronization is requested through the event rule processing engine, the synchronization engine creates an ActiveML instance (CActiveMLParser) for the file that needs to be synchronized, transfers it to the server (CSyncDataTransfer), and analyzes the ActiveML instance sent from the server (CActiveMLParser). Send the necessary file information to the security engine.

Example Configuration 3. Data Recovery Module (Added)

-Complete or partial recovery using server data in case of PC or file loss

-Complete recovery: Recover all data using server data when all data on PC is lost

Partial recovery

In the present embodiment, a data recovery engine has been developed that can be completely or partially recovered using data backed up to a server when a PC or a specific file is lost. Complete recovery is a method of downloading and recovering all the final version files from the files backed up to the server when the user PC is replaced or the disk is formatted. Partial recovery is a method of recovering only the desired files by specifying a recovery point. It is divided into time-based recovery and version-based recovery method according to user's recovery point designation method.

The backup solution according to the present embodiment operates by uploading the changed file to the server whenever an event occurs. Therefore, the server can have several backup files per time for one file name, and these backup files for each time zone are called version files. In the present embodiment, a recovery engine capable of performing a final backup file recovery, a timephased recovery, and a specific version file recovery function has been developed for a version file. 16 is a flowchart of a data recovery engine applied to this embodiment.

In FIG. 16, the recovery location selection option is an option for selecting a location of a folder and a file to be restored by complete recovery or partial recovery. The user can select and use a specific location (eg D: \ recovery folder), or if not selected, create a folder in the original location before the backup and restore the file.

At this time, the option to select a solution for the case where a file with the same name as the file to be recovered during the file recovery exists in the user's PC may be further selected as a file duplication solution selection option. Table 10 lists the options for resolving file duplication.

Option to choose file resolution solutions Way Explanation Overwrite -Overwrite existing file with recovered file-In conclusion, only one recovered file exists on PC Modify Recovery File Name -Modify the name of the recovered file by adding (1), (2) ... to the name of the file to be recovered-Existing file with the same name still exists-ex) Final report.hwp-> Final report (1) .hwp Edit version file name -When recovering several version files with the same file name at the same time, since the file name is duplicated, modify the recovery file name by adding “backup time” information to the name of the version file being recovered.-Existing file of the same name still exists-Yes ) Final Report.hwp-> Final Report_20080312.hwp, Final Report_20070320.hwp

Example Configuration 4. Encryption module for data protection on upload / download (additional)

-File encryption for data protection in case of network / server hacking

-Upload after pre-encryption on PC before upload

-Encryption method by Password Based Encryption

-Encryption processing module using various public encryption algorithms such as AES, RC4, RC5, DES, 3DES

This embodiment, which combines the above embodiments, is composed of a client system for real-time automatic backup and recovery, synchronization of distributed files, and a server system for supporting recovery and management functions along with server disk functions. Table 11 describes the detailed functions for each type of the present invention solution.

Function of this solution System classification Functional classification Detail function Client system Auto backup -Automatic backup when events occur, such as file creation / modification, etc.-Real time backup-Scheduled backup by user definition-File encryption using individual password-Log management related to backup-Automatic window system shutdown after backup completion Distributed File Synchronization -Synchronization of files distributed on multiple PCs-Automatic recovery by synchronization-Detection and resolution of inconsistency for synchronization files Server systems restore -Support web disk function through browser-Only last version file recovery-Time-based file recovery-Version-based file recovery management -Automatic backup history management-User personal information management-Usage status management by user

The client system of this solution is mainly equipped with real-time automatic backup and synchronization of distributed files. This client system installs on the user's PC in the Windows operating system environment, designates the destination folder for automatic backup, and automatically synchronizes the server and user PC data by automatically backing up the changed file to the server whenever an event such as file creation, modification, or deletion occurs. do.

Once the client system has been successfully installed on your PC, the login screen will launch. Enter the user ID and password to log in and connect to the server system of this solution. In the login screen, you can save the user ID or select the option to log in automatically when the program starts. 18 is a login screen of the client system.

After installing the client system, the user can set various items related to the backup through the automatic backup setup wizard at first login.

Computer name setting is a step in which a user sets a PC name to identify a backup target PC. The computer name set in this step is used to distinguish the user's multiple PCs from the server system of this solution.

17 is a screen of a step of setting a computer name of a client system.

The backup folder setting step is to specify the target folder for automatic backup. You can specify one or more folders and delete them. In the system implementing the present invention, all folders except the system folder (for example, C: \ WINDOWS, C: \ Program Files, etc.) and the disk root folder (for example, C: \ and D: \) of the user PC are backed up. Can be specified as 20 is a screen of a step of setting a backup target folder.

In this embodiment, both an automatic backup method and a user-defined periodic scheduled backup method are supported. You can choose to use both automatic and scheduled backups, or you can specify only one method. Basically, it supports 'Auto Backup' method which can automatically back up every file change event.

Automatic backup supports 'auto backup' when a file change event occurs, and 'backup every schedule' by setting a backup timer.

‘Automatic backup’ method checks the condition of an event as soon as a file change event occurs and if the scan result is true, synchronizes the backup immediately.

 'Backup every schedule' method does not determine conditions immediately when an event occurs, but temporarily stores the information, time, and change event type of the file where the event occurred. In addition, when a certain amount of time (eg 30 minutes) elapses compared to the previous backup time, the condition of the event is checked and if the test result is true, it is synchronized and backed up. This method can be used by the user when the load on the system is increased due to the automatic backup that occurs every time the file is changed or when adjustment is necessary because there are many version files that are backed up every time it is saved.

Scheduling backup is a method for user to specify the information of 'week, day, hour, minute' to synchronize and back up and restore the information about the changed file at a specific date and time. This backup method can be used when the user does not use the PC for a long time and the user wants to perform the backup during the rest period when the load on the user PC is low.

The encryption setting step is a step of selecting whether or not to encrypt a file with a password specified by a user when the file is backed up and transmit it to the server. In the system implementing the present invention, after encrypting using an AES encryption algorithm, a file is transmitted to a server. 19 is a screen of a step of setting a backup cycle and whether to encrypt a file.

After completing the automatic backup setup wizard, all files in the set backup destination folder are backed up to the server to synchronize the user PC with the server. 22 is a screen for encrypting and backing up all files in the backup destination folder to the server after completing the automatic backup setup wizard.

After the first automatic backup, automatic backup is executed according to the backup cycle in the user's PC to back up or restore files by synchronizing only the information about the changed files.

The backup administrator can set up user information and backup related information, and 'Backup' menu that allows users to execute backup arbitrarily, 'Recovery' menu that allows users to perform full and partial recovery by accessing the web disk. It consists of a menu. On the Backup Manager screen, you can check the number of files and folders that are being backed up. You can check the encryption / decryption and backup progress and completion status. 21 is a main screen of the backup manager of the client system of the present solution.

The environment setting is largely composed of user information settings for managing user information and backup information settings for managing backup information. This configuration is used to modify and manage the user information and backup information specified through the automatic backup setup wizard at the first login.

In the user information setting menu, you can manage information such as changing the user's password, whether to run automatically when Windows starts, whether to log in automatically when the program is executed, and saving ID / password. You can add or delete backup folders in the backup information setting menu. In addition, you can set backup cycle management and file encryption using 'Automatic Backup' and 'Periodic Backup'. 22 is a user information setting screen, and FIG. 23 is a backup information setting screen.

On the other hand, the server system of the present embodiment is composed of a recovery function that can perform a complete recovery and a partial recovery, a web disk function that can retrieve information backed up from the user PC through a browser, and a disk usage status management function for each user.

You can run the Recovery Wizard by selecting the 'Recovery' menu on the client system of the solution in case you need to recover your PC files.

At this time, it provides a full recovery to recover all the last versions of the backed up files and a partial recovery method to recover only a specific point in time or a specific version of a file. Table 12 shows a recovery method provided in this embodiment, and FIG. 24 shows a screen for selecting a recovery method desired by a user.

Recovery method Classification Recovery method Explanation Full recovery Full recovery of the last backup version file -If all the data on the PC is lost, such as formatting, download all files of the last backup version of the file backed up to the server and recover all folder structure. Partial recovery Version based partial recovery -Selective recovery for specific folders or files-How to recover by selecting the folder or version file you need to recover Point-Based Partial Recovery Selective recovery by specifying a specific date

Full backup version file recovery restores both the final version file and the backup folder structure among the version files backed up to the present.

Version-based partial recovery provides an explorer-like interface to restore the folder structure and specific version files by selecting multiple folders or files for recovery. FIG. 25 is a screen of an explorer type in which a folder or a file to be recovered may be selected.

Point-in-time partial recovery can retrieve the history information backed up by selecting a specific date that needs to be restored through a calendar interface. You can select the date and time zone for recovery and restore the folders and files backed up at that time. 26 is a screen for selecting a specific time point for recovery.

Duplicate file processing is a step of selecting a file name processing method when a file with the same name as the file to be recovered exists on the user's PC during the recovery process. For file name duplication, you can choose one of the following methods: Overwrite File, Automatically Change Recovery File Name, and Add Version Information to File Name. 27 is an option selection screen for processing duplicate file names.

The Recovery Wizard allows you to check the settings for the recovery method, recovery destination, and duplicate file name resolution you have specified. You can also perform a recovery by clicking on the 'Start Recovery' button. 28 is a screen for confirming recovery setting items through the recovery wizard.

The restore operation can specify the recovery destination folder where the recovery file will be stored. You can check the recovery progress time, progress status, and the number and size of recovery files. When recovery is executed, all files to be recovered are downloaded from the server to the user's PC and decrypted to complete the recovery. 29 is a screen for executing recovery after completion of the recovery wizard.

The server system has developed a web disk function that allows users to search for files automatically backed up through the web. When the user logs in to the server system, the backed up files can be checked through the automatic backup list screen in the form of a explorer. Each file can be checked by the modified version file, and each PC can be checked on which PC has been modified and uploaded. The user can select and download the necessary backup files via the web disk and check the status of the backed up folders and files. 30 is a main screen of a web disk provided by a server system.

On the server system, you can check the backup history by date. You can check the backup time by date selected by user, the number of folders and files backed up in real time, the name of the backup target PC, and search the list of files backed up by each time. 31 is an automatic backup history management screen for each date provided by a server system.

While the embodiments of the present invention have been described in detail with reference to the drawings, the technical spirit of the present invention is not limited to the above embodiments.

In other words, those of ordinary skill in the art to which the present invention pertains may utilize the technical spirit contained in the specification and drawings of the present invention, and as necessary, simple modifications and simple changes that are not included in the specification and drawings of the present invention. An extended example may be further implemented, but this is also obviously included in the scope of the technical idea uniquely possessed by the present invention.

 In the present invention, it is possible to secure a price competitiveness by supplying a low cost product to the existing backup solution by developing a system that can operate independently of a PC-class server. It is expected to replace imports on royalty payments due to the introduction of expensive servers and the use of commercial software.

In addition, when the present invention is widely used in the enterprise or industrial sites, it is possible to provide a secure security function even for server / network hacking of important data of the enterprise by the security function of pre-encryption and uploading from a PC.

1 is a diagram representing a framework of SyncML.

2a and 2b is a conceptual view of the operation of a typical database and active database.

3 is a schema structure diagram of the present invention ActiveML for defining synchronization data.

4 is a conceptual diagram of a One-way sync from client only synchronization protocol.

5 is a conceptual diagram of a One-way sync from server only synchronization protocol.

6 is a conceptual diagram of a Two-way sync synchronization protocol.

7 is a flow chart for detecting and resolving inconsistencies between server and PC data.

8A and 8B are diagrams illustrating an operation method of the existing backup solution and an operation method of the present invention.

9 is a conceptual view of the operation of the backup solution of the present invention.

10 is an operation scenario of the operation concept of FIG.

11 is a conceptual diagram of an event rule processing engine based on an ECA model mounted on the present embodiment.

12 is an operational flow diagram of the event rule processing engine of FIG.

Figure 13 is a class schematic diagram for the event rule processing engine expressed in UML.

14 is a conceptual diagram of data synchronization between a server disk and a PC according to the present embodiment.

15 is a class schematic diagram of a synchronization engine expressed in UML.

16 is a conceptual scenario of a data recovery engine applied to this embodiment.

Fig. 17 is a flowchart of a data recovery engine applied to this embodiment.

18 is a login screen of a client system.

19 is a screen of a step of setting a computer name of a client system.

20 is a screen of a step of setting a backup cycle and whether to encrypt a file.

21 is a screen of a step of setting a backup target folder.

Fig. 22 is a screen for executing a backup after completion of the automatic backup setup wizard.

23 is a backup manager main screen of a client system.

24 is a user information setting screen;

25 is a backup information setting screen;

Fig. 26 is a screen for selecting a recovery method desired by a user;

Fig. 27 is a screen in the form of an explorer in which a folder or file to be recovered can be selected.

28 is a screen for selecting a specific point in time for which recovery is necessary.

Fig. 29 is an option selection screen for processing duplicate file names.

30 is a screen for confirming recovery setting items through the recovery wizard.

Fig. 31 is a screen for executing recovery after completion of the recovery wizard;

32 is a main screen of a web disk provided by a server system.

33 is an automatic backup history management screen for each date provided by the server system.

Claims (11)

delete A data synchronization method for synchronizing, storing, calling, transferring and deleting data stored in a computer between at least one server and one or more PCs, Generating at least one or more occurrence identifiers and at least one alteration identifier generated and modified after the generation time of the occurrence identifiers in the data structure including the data; and Classifying and deleting data to be deleted in the PC based on at least one of the identifiers; And, And synchronizing the storage object or the call object or the object data existing in the server or the PC based on the other one or more of the identifiers other than the one or more identifiers. The identifier as a reference for classifying the data to be synchronized and deleted is a change identifier of at least one of the identifiers, a change identifier generated by combining at least two change identifiers, or at least one occurrence identifier and at least one And a change identifier generated by combining the change identifier. The method of claim 2, The local occurrence identifier (LF), which is one of the generation identifiers, is a character string having a predetermined length to which a predetermined value is given when predetermined data is first generated or stored in the PC, and identifies data of each PC. And the only value is that the predetermined value does not change when a predetermined event occurs in the predetermined data synchronization process. The method of claim 2, A global occurrence identifier (GF), which is one of the generation identifiers, is a character string having a predetermined length to which a predetermined value is given when predetermined data is first generated or first stored in the PC, and the same file distributed in multiple PCs. The only value for identifying the data synchronization method, characterized in that the predetermined value does not change when a predetermined event occurs in the predetermined data synchronization process. The method of claim 3, The event change identifier (CM), which is a change identifier of any one of the change identifiers, is a string of numbers to which an event value is assigned when a predetermined event is first generated in the predetermined data in the PC, and after the predetermined event, the PC is changed. Whenever another predetermined event occurs in the data synchronization method, the corresponding event value is given only in the PC. The method of claim 5, The time change identifier LM, which is any one of the change identifiers, is a string of numbers to which a time value when a predetermined event occurs in the predetermined data in the PC is assigned. Whenever a predetermined event occurs, a corresponding time value is assigned only to the PC. The method of claim 5, The synchronization change identifier (SM), which is any one of the change identifiers, is a string of numbers to which a time value when synchronization occurs for the predetermined data is transmitted between the PC and the server. Whenever occurs, the corresponding time value is given to the server and the PC. delete delete delete delete

Images