JP2005284842A - Data backup system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a data backup system that facilitates reconstruction upon an accidental failure in terminal equipment by sending and saving backup data of the terminal equipment to a data backup server via a network. <P>SOLUTION: The data backup system 10 using the network 300 is so designed that the terminal equipment 100 performs an autonomous data backup operation in the background of normal operations and that the terminal equipment 100 and the data backup server 200 segment backup data into a predetermined data size to exchange them as packets. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a technology for backing up various data using a network.

Conventionally, for example, a data backup service has been provided in which file data backup in a personal computer is performed via a network. Such a data backup service generally uses a web browser or the like to specify data that the user wants to back up, for example, in units of files.
However, in such a data backup service, for example, in the event of a sudden failure of a personal computer, only files that are backed up are rescued. Therefore, for a failed personal computer, a recovery operation for re-installation from the OS (operating system) is indispensable, and a so-called reversion operation in case of an unexpected failure becomes large.

By the way, regarding data backup of a personal computer or the like, there is a strong demand for facilitating the recovery work by replacing only the defective portion with respect to a failure such as an unexpected failure without involving human work.
On the other hand, there has been a remarkable increase in the performance of personal computers and the like in recent years, and the performance sufficient for use as a man machine is already sufficient, and the CPU power is excessive. Also, the Internet connection environment in ordinary homes has been generalized by so-called broadband continuous connection, and a network environment capable of broadband data communication has been established.
Therefore, it has become possible to packetize backup data using such surplus CPU power of a personal computer and transmit it to a data backup server, but such a data backup system does not exist.

On the other hand, Patent Document 1 discloses an OS failure recovery method for recovering the operating state before the failure occurs when a failure occurs in the OS of the information processing apparatus.
According to this configuration, OS backup data is stored in advance in a large-capacity recording medium, and when a failure occurs, the information processing apparatus is activated by the activation OS recorded on the recording medium, and the data is stored in the recording medium. The stored backup data is overwritten in a predetermined storage area of the storage device in which the OS in which the failure occurred is recorded.

Patent Document 2 discloses a backup system that can easily perform complete backup and restoration including a system area on an electronic computer regardless of the type of OS.
According to this configuration, the computer is connected to the server via the network, and the startup OS of the computer and the recorded contents of the hard disk of the computer are stored on the server side via the network, and the startup OS By executing the backup function or the restore function, the contents of the hard disk of the electronic computer can be easily backed up or restored.

Further, Patent Document 3 discloses a system data backup method in which a system data backup process is executed without stopping the system when backup does not end normally on the host computer.
According to this configuration, when backup does not end normally on the host computer, the system data to be backed up is transferred to the other host computer connected to the host computer via the network, and the host computer transfers this data. Data is directly stored in a recording medium.

Patent Document 4 discloses a data backup / restoration method and system in a multiple computer system environment.
According to this configuration, a plurality of terminal data are pooled on one host computer to which a plurality of terminals are connected by a network, and one terminal is connected to any terminal from the host computer via the network. An arbitrary terminal environment can be reproduced by transferring data.

Finally, Patent Document 5 discloses a video on demand system that prevents unauthorized data backup.
According to this configuration, when the video client requests the video server for data backup, the hard disk volume serial number in which the OS is stored is read and sent to the server. As a result, the server compares the volume serial number with the volume serial number for data backup permission stored in advance, and permits data backup if they match.
JP 2002-041317 A JP 2002-358245 A Japanese Patent Application Laid-Open No. 07-160651 JP-A-10-133959 Japanese Patent Laid-Open No. 11-220718

However, the data backup according to Patent Documents 1 to 5 described above has the following problems.
That is, in the OS failure recovery method according to Patent Document 1, a normal recovery operation is required in which the boot OS and backup data are simply saved in a storage medium, and the failed information processing apparatus is recovered by these. It does not facilitate the recovery work, and the return work becomes large.

  Further, in the backup system according to Patent Document 2, the backup work is performed by executing an application on the electronic computer, and the restoration function is executed from the boot OS on the electronic computer when the restoration is performed. It is supposed to run. For this reason, the user needs to execute the application consciously every time backup is performed, and the restoration work is not as easy as in the case of Patent Document 1, and the backward work becomes large.

  Furthermore, in the system data backup method disclosed in Patent Document 3, there are a plurality of host computers, and when the host computer as the server is down, another host computer acts as the server. Therefore, the server system is backed up, and the recovery work is not performed in the event of an unexpected failure of an individual personal computer.

  Further, in the backup / restoration method and system disclosed in Patent Document 4, a plurality of terminal data is pooled on a host computer, and the system environment of an arbitrary terminal using terminal data pooled on the host computer. It is intended to reproduce the above, and is not intended to perform recovery work in the event of an unexpected failure of an individual personal computer.

  Finally, in the video on demand system according to Patent Document 5, the storage destination of the data backup from the video server is collated with the volume serial number of the hard disk of the video client to determine whether or not the data backup is possible. In the event of an unexpected failure of an individual personal computer, recovery work is not performed.

  The present invention has been made to solve the above-described problems, and uses backup CPU power of a terminal device such as a personal computer to packetize backup data and send it to a data backup server via a network. Data that is stored in the data backup server and received as packetized backup data from the data backup server via the network as needed, allowing easy reconstruction in the event of a terminal device failure The purpose is to provide a backup system.

  In order to achieve this object, a data backup system according to claim 1 of the present invention receives backup data sent from a terminal device via a network by a data backup server, stores it in a storage device, and stores the data When a backup server has a restore request from the terminal device, in the data backup system that transmits backup data corresponding to the terminal device to the terminal device via the network, the terminal device performs operations related to data backup, In addition to performing autonomously in the background of normal operation, the terminal device and the data backup server send and receive backup data in a predetermined data size, and the terminal device is registered in advance with the data backup server. , Terminal When the backup start or restore service start command is sent to the data backup server, the terminal identification information and password are also sent, and the data backup server issues a service start command from the terminal device. When received, the terminal identification information and the password that are sent at the same time are collated to determine whether or not the terminal device can be serviced.

  When the data backup system has such a configuration, the terminal device autonomously performs operations related to data backup in the background of its normal operation, and transmits backup data to the data backup server via the network. The backup data is automatically transmitted to the data backup server and stored without the user of the terminal device being particularly conscious of the backup.

When backup data is required, a restore service start command is transmitted from the terminal device to the data backup server via the network, so that the backup data is transmitted from the data backup server to the terminal device via the network. It is transmitted with a predetermined data size.
At that time, by transmitting terminal identification information and a password from the terminal device to the data backup server, the data backup server determines whether or not the terminal can be serviced by checking the terminal identification information and the password, Backup data of a certain terminal device is not transmitted to other terminal devices.

  Furthermore, when backup data is transmitted / received, the traffic volume of the network does not increase sharply because the data is segmented into a predetermined data size and transmitted / received.

The data backup system according to claim 2 is configured such that the predetermined data size is selected so as not to give a burst load to the buffering resources of the network.
When the data backup system has such a configuration, the bursting load is not applied to the buffering resources of the network by the transmission / reception of the backup data between each terminal device and the data backup server.

The data backup system according to claim 3 is configured such that the predetermined data size is determined between the terminal device and the data backup server at the start of transmission / reception of backup data.
When the data backup system has such a configuration, based on the physical line speed of the network, the connection speed of the terminal device to the network, the data transmission / reception bandwidth that can actually be used, or the number of terminal devices connected to the network, By determining the data size at the time of transmission / reception of backup data between the terminal device and the data backup server, a data size corresponding to the traffic volume of the network at that time is selected. A congestion state can be avoided and the load on the network is not great.

The data backup system according to claim 4 is configured such that the predetermined data size is changed between the terminal device and the data backup server during the transmission / reception of the backup data.
When the data backup system has such a configuration, when the amount of network traffic suddenly changes during the transmission / reception of backup data between the terminal device and the data backup server, such a change can be handled. Because the data size is dynamically changed, the data size is selected according to the network traffic volume at that time, enabling efficient data transfer according to the network traffic volume at that time. Therefore, it does not become a great load on the network.

The data backup system according to claim 5 is configured such that the terminal identification information is terminal-specific information such as a terminal's MAC (Media Access Control Address) address and a given IP (Internet Protocol) address.
When the data backup system has such a configuration, since the terminal device is collated based on the terminal-specific information, the backup data of a certain terminal device is not transmitted to other terminal devices. In addition to maintaining confidentiality, the data backup server further provides a storage device for storing backup data, so that, for example, RADIUS (Remote Authentication Dial-) defined in RFC (Request for Comments) 2865 is provided. It is also possible to provide system extensibility through server cooperation using an In User Services procedure.

The data backup system according to claim 6 is configured such that the terminal identification information includes user identification information such as a user identifier of a user who operates the terminal device.
When the data backup system has such a configuration, the terminal device is verified based on the terminal-specific information, and when another person tries to acquire backup data on the terminal device based on the user identification information, Such transmission of backup data will be blocked.

Thus, according to the present invention, the terminal device autonomously performs operations related to data backup in the background of its normal operation, and transmits backup data to the data backup server via the network. The user of the terminal device is particularly conscious of the backup, and the backup data is automatically transmitted to the data backup server and stored without performing an operation such as starting an application for backup.
When backup data is required, a restore service start command is transmitted from the terminal device to the data backup server via the network, so that the backup data is transmitted from the data backup server to the terminal device via the network. It is transmitted with a predetermined data size.
Therefore, the backup operation can be performed easily and reliably, and the return operation in the recovery operation in the event of an unexpected failure of the terminal device is reduced.

  In addition, when transmitting / receiving backup data, data is transmitted and received after being segmented into a predetermined data size. There is no such thing as a typical load.

  Embodiments of the present invention will be described below with reference to the drawings.

An embodiment of the data backup system of the present invention will be described with reference to FIG.
FIG. 1 is a block diagram showing the configuration of the data backup system.

As shown in FIG. 1, the data backup system 10 includes a terminal device 100, a data backup server 200, and a network 300.
Here, the network 300 is a network (a network such as a general public line network or a dedicated line network) including a network in which terminals and servers connect to the Internet and an Internet connection provided by a provider, and provides an Internet connection service. To do.

The terminal device 100 is registered in advance in the data backup service provided by the data backup server 200, is given user identification information 101 and a password 102, and is terminal-specific information such as a MAC address and an IP address described later. 103.
In FIG. 1, two terminal devices 100 are illustrated, but actually, a large number of terminal devices 100 are connected to the data backup server 200 via the network 300.

  The terminal device 100 is a personal computer or the like having a known configuration, and performs a normal operation by various applications and performs a data backup operation in the background of the normal operation. Therefore, since the normal operation is not related to the data backup operation according to the present invention, the description thereof is omitted.

As shown in FIG. 2, the terminal device 100 includes a control unit 110, a storage device 120, a network interface 130, and a functional module 140.
The control unit 110 is operated by the OS and controls the storage device 120, the network interface 130, and the functional module 140 to realize various functions.

  The network interface 130 is connected to the network 300 and has means for transmitting / receiving backup data to / from the data backup server 200 via the network 300 by accessing the data backup server 200 via the network 300. For example, it has a communication function such as TCP / IP or VoIP as a communication protocol.

  The functional module 140 holds the terminal-specific information 103, the user identification information 101, and the password 102 described above. When the service start command 141 is sent to the data backup server 200, the terminal-specific information 103 is stored. , The user identification information 101 and the password 102 are sent together.

  The terminal device 100 performs data backup on a disk array or file basis, and the disk array backup may include an OS, so the storage device 120 and the network interface 130, which are hardware, are included. On the other hand, device control is performed at the BIOS level without going through the OS, and for each file backup, since each file is under the file system control by the OS, device control is done through the OS, that is, at the OS level. To do.

Here, when performing data backup, the functional module 140 of the terminal device 100 sends a backup or restore service start command 141 from the network interface 130 via the network 300, the terminal specific information 103, the user identification information 101, and Send with password 102.
Here, the service start command 141 includes a backup or restore command, a connection condition such as a physical line speed of the network interface 130 to the network 300, a bandwidth amount actually effective on the network 300, and backup data to be backed up. According to these, backup or restoration for the block ID of the backup data is instructed.
For the bandwidth, for example, a round trip time of an ICMP (Internet Control Message Protocol) message that dynamically measures a delay in the network 300 between the terminal device 100 and the data backup server 200 may be used. .

  Next, the functional module 140 of the terminal device 100 receives a response indicating whether or not the service start command 141 is accepted from the data backup server 200. When the service is possible, the backup module reads the backup data and backs up the packet. The packetized backup data transmitted from the network interface 130 to the data backup server 200 via the network 300 or transmitted from the data backup server 200 via the network 300 at the time of restoration. Is received, restored to the original backup data, and stored in the storage device 120.

The functional module 140 of the terminal device 100 ends the backup operation when the service is not possible.
The functional module 140 of the terminal device 100 transmits a service start command 141 to the data backup server 200 via the network 300 again when there is no response from the data backup server 200 regarding whether or not service is possible. .
On the other hand, when a plurality of service availability responses are received from the data backup server 200, the functional module 140 of the terminal device 100 makes the last response valid and performs the subsequent processing.

  On the other hand, as shown in FIG. 1, the data backup server 200 includes an interface unit 210, a service determination unit 220, a terminal information database 230, a data processing unit 240, and storage devices 250 and 260. It is configured.

The interface unit 210 is connected to the network 300 and interconnects the terminal devices 100 connected via the network 300 as a LAN.
The interface unit 210 may assign a dynamic IP address to each terminal device 100 connected via the network 300 and transmit the IP address to the terminal device 100.
Further, the interface unit 210 divides and packetizes the data at a predetermined data size at the time of restoration, and transmits the packetized backup data to the terminal device 100 via the network 300.

  The service determination unit 220 reads the terminal unique information 103, the user identification information 101, and the password 102 of each terminal device 100 registered in advance in the terminal information database 230, and performs service from each terminal device 100 via the network 300. The terminal exchange information 103, the user identification information 101, and the password 102 transmitted together with the start command 141 are collated to determine whether the service for the terminal device 100 is possible.

  When the service determination unit 220 determines that the service is possible, the service determination unit 220 is connected to the data backup server 200 via the network 300 and the connection condition between the terminal device 100 and the data backup server 200. The optimal data size is calculated in the network 300 according to the number of the terminal devices 100 that are present, and further the traffic of the network 300 and the capacity of the storage devices 250 and 260. The data is transmitted to the interface unit 210 and to the terminal device 100 via the network 300.

In addition, the service determination unit 220 sends the determination result of the service availability and the service start command 141 to the data processing unit 240.
Furthermore, when the service determination unit 220 determines that the service is not possible, the service determination unit 220 transmits a determination result indicating that the service is not possible to the terminal device 100 via the network 300.

In the case of backup based on the determination result of service availability from the service determination unit 220 and the service start command 141, the data processing unit 240 then transmits backup data transmitted from the terminal device 100 via the network 300. Is stored in the storage device 250 or 260 in association with the user identification information 101 or the terminal specific information 103.
In the case of restoration, the data processing unit 240 determines the terminal-specific information of the terminal device 100 from the storage device 250 or 260 based on the determination result of service availability from the service determination unit 220 and the service start command 141. 103 or the user identification information 101 is read out and transferred to the interface unit 210.

Next, the operation of the data backup system of this embodiment will be described with reference to FIGS.
The data backup system includes a control operation of the terminal device shown in FIG. 3, a control operation of the data backup server shown in FIG. 4, a data write control operation in the backup shown in FIG. 5, and a data write control operation in the restore shown in FIG. Used at each step.

First, control operations of the terminal device and the data backup server will be described with reference to the flowcharts of FIGS.
In step C101 of FIG. 3, the terminal device 100 sends a service start command 141 including the terminal specific information 103, the user identification information 101, the password 102, the service type (backup or restore command), connection conditions, etc. The data is transmitted to the data backup server 200 via 300.
On the other hand, the interface unit 210 of the data backup server 200 receives this service start command 141 and transfers it to the service determination unit 220 in step S101 of FIG.

  As a result, the service determination unit 220, in step S102 of FIG. 4, stores the terminal specific information 103, the user identification information 101, and the password 102 included in the service start command 141 in the terminal information database 230. The service 103 is checked against the information 103, the user identification information 101, and the password 102 to determine whether the service is possible. Here, if the service is not possible, the service determination unit 220 transmits a determination result indicating that the service is not possible to the terminal device 100 from the interface unit 210 via the network 300 in step S102a. Return to a RTS.

  If the determination result indicates that the service is acceptable in step S102, in step S103, the service determination unit 220 sends the determination result indicating that the service is possible (service start acceptance (ACK)) and the service start command 141 to the data processing unit. To 240. At this time, in practice, the service determination unit 220 extracts, for example, a block ID and a command to be backed up and sends them to the data processing unit 240 in order to reduce transfer data.

At the same time, in step S104, the service determination unit 220 determines the connection conditions included in the service start command 141 and the processing capacity of the data backup server 200 such as the number of terminal devices 100 connected to the data backup server 200. Then, an optimal data size is determined, and this data size is transmitted to the terminal device 100 from the interface unit 210 via the network 300 together with a determination result of service availability as a service start acceptance message.
In response to this, when the terminal device 100 receives the determination result indicating that the service is not possible in step C102 of FIG. 3, the functional module 140 stops the backup operation in step C102a and returns to the initial state (RTS). .

  Subsequently, in the data backup server 200, in step S105 of FIG. 4, the service determination unit 220 determines a command included in the service start command 141, and sends an instruction to backup or restore to the data processing unit 240. To do.

Here, the case of backup will be described below.
In the terminal device 100, in step C103 of FIG. 3, the functional module 140 of the terminal device 100 performs a packetizing operation on the disk array or file to be backed up according to the data size sent from the data backup server 200. The OS or the interface of the storage device 120 is notified, and the backup data is read out and packetized in step C104 of FIG. 3 and transmitted from the network interface 130 to the data backup server 200 via the network 300.

In response to this, the service determination unit 220 of the data backup server 200 receives the packetized backup data in step S106 of FIG. 4 and extracts the block ID of the received backup data in step S107. By comparing with the block ID included in the service start command 141, it is determined that the backup data is from the terminal device 100 having the service start command 141, and the backup data is transferred from the interface unit 210 to the data processing unit 240. To be transferred.
Accordingly, after the service determination unit 220 confirms the last packet of the backup data, that is, the block end in step S108, the service determination unit 220 confirms the block size up to the final packet in step S109.

If the block size is a processable size, the service determination unit 220 transmits a backup data reception response (ACK) from the interface unit 210 to the terminal device 100 via the network 300 in step S110. To do.
In response to this, the functional module 140 of the terminal device 100 receives this backup data reception response (ACK) in step C105 and returns to the initial state.
In step S111, the data processing unit 240 secures the block size and writes the backup data accumulated from the first packet to the storage device 250 or 260.

If it is determined in step S109 that the block size is not a capacity that can be processed by the data processing unit 240, the service determination unit 220 returns a backup data reception rejection response (NACK) in step S112. The data is transmitted from the interface unit 210 to the terminal device 100 via the network 300.
In response to this, when receiving the backup data reception rejection response (NACK) in step C105, the functional module 140 of the terminal device 100 returns to step C104 and retransfers the backup data.

Next, the case of restoration will be described below.
In the terminal device 100, in step C103 of FIG. 3, the functional module 140 of the terminal device 100 starts data reception and reading processing.
On the other hand, in the data backup server 200, in step S <b> 105, the service determination unit 220 sends the read processing command and the terminal specific information 103 to the data processing unit 240. Thereby, the data processing unit 240 reads the backup data associated with the terminal specific information 103 from the storage device 250 or 260 and transfers it to the interface unit 210.
Thereafter, when the data processing unit 240 transfers the backup data to the interface unit 210 until the block end of the backup data, the data processing unit 240 temporarily closes the backup data file and waits for a response from the terminal device 110.

Then, in step S113, the interface unit 210 subdivides the packet into the data size and adds information necessary for blocking, such as a block ID, to the terminal device 100 via the network 300. To send.
At that time, the interface unit 210 adds information indicating the final data to the block ID of the final packet, and transmits the information to the terminal device 100.

In response to this, the functional module 140 of the terminal device 100 receives the packetized backup data in Step C106 of FIG. 3, extracts the block ID of the received backup data in Step C107, and performs Step C108. Then, it is determined whether or not the backup data is related to the terminal device 100.
When the backup data is related to the terminal device 100, the functional module 140 transmits a backup data reception completion response (ACK) to the data backup server 200 via the network 300 in step C109. Thereafter, in step C110, the received backup data is written into the storage device 120, and then the restore process is terminated.

On the other hand, when the data backup server 200 receives the backup data reception completion response (ACK) from the terminal device 100 in step S115, the interface unit 210 sends the backup data reception completion response to the service determination unit 220 and the data. Transfer to the processing unit 240.
Then, in step S116, the data processing unit 240 deletes the backup data from the storage device 250 or 260, and if there is a file deletion command in the service start command 141, deletes the file in step S117, Return to the initial state (RTS).

If the backup data is not related to the terminal device 100 in step C108, the functional module 140 sends a backup data reception rejection response (NACK) to the data backup server 200 via the network 300 in step C111. To the initial state (RTS).
In response to this, when the data backup server 200 receives a backup data reception rejection response (NACK) from the terminal device 100 in step S115, the interface unit 210 sends the backup data reception rejection response to the service determination unit 220 and the data. Transfer to the processing unit 240 and return to the initial state (RTS).
This completes the backup and restore operation.

Next, a detailed data write control operation in backup will be described with reference to the time chart of FIG.
First, as shown by symbol A1, when a service start command 141 is transmitted from the terminal device 100 to the data backup server 200, the data backup server 200, as shown by symbol A2, determines whether or not a service is possible, ie, a service start. Acknowledgment (ACK) is transmitted to the terminal device 100, and an initial area for writing backup data is secured in the storage devices 250 and 260 as indicated by reference numeral A3.
This completes the initial setting.

Subsequently, as indicated by reference signs A4 to A5, backup data is sequentially transmitted from the terminal device 100 to the data backup server 200 in units of blocks. When packetized backup data having a predetermined data size is transmitted, the data backup server 200 writes the backup data having the predetermined data size in the storage devices 250 and 260 as indicated by reference numeral A6. , A backup data reception completion response (ACK) is transmitted to the terminal device 100, as indicated by reference numeral A7.
In response to this, the terminal device 100 transmits the backup data to the data backup server 200 in units of blocks as indicated by reference numerals A8 to A9 again.
When the backup data of the final block including the final packet is transmitted from the terminal device 100 to the data backup server 200 as indicated by reference numeral A9, the data backup server 200 transmits the backup data as indicated by reference numeral A10. After the data is written into the storage devices 250 and 260, a backup data reception response ACK is transmitted to the terminal device 100 as indicated by reference numeral A11.
Thus, the backup writing process by normal operation is completed.

Here, as indicated by reference signs A12 to A13, when backup data up to the last block is transmitted from the terminal device 100 to the data backup server 200, an abnormality occurs and the block size cannot be processed. The data backup server 200 discards the backup data write data as indicated by reference numeral A14 and sends a backup data reception rejection response (NACK) to the terminal device 100 via the network 300 as indicated by reference numeral A15. Send.
This completes the backup writing process due to the abnormal operation.

Next, a detailed data read control operation in restoration will be described with reference to the time chart of FIG.
First, as shown by reference numeral B1, when a service start command 141 is transmitted from the terminal device 100 to the data backup server 200, the data backup server 200 determines the service availability determination result, that is, the service start, as shown by reference numeral B2. An acknowledgment (ACK) is transmitted to the terminal device 100.
This completes the initial setting.

Subsequently, as indicated by reference numeral B3, the data backup server 200 reads backup data from the storage devices 250 and 260, and sequentially transmits the backup data to the terminal device 100 in units of blocks as indicated by reference numerals B4 to B5. Thus, when the terminal device 100 receives backup data of a predetermined size, the terminal device 100 transmits a backup data reception completion response (ACK) to the data backup server 200 as indicated by reference numeral B6.
In this way, as shown by reference numeral B7, the data backup server 200 reads backup data including the final packet from the storage devices 250 and 260, and as indicated by reference numerals B8 to B9, the backup data including the final block is data. When transmitted from the backup server 200 to the terminal device 100, the terminal device 100 transmits a backup data reception response ACK to the data backup server 200 as indicated by reference numeral B10.
This completes the restore reading process by normal operation.

Here, as indicated by reference numeral B11, the data backup server 200 reads the backup data from the storage devices 250 and 260, and as indicated by reference numerals B12 to B13, the backup data up to the final block is transferred from the data backup server 200 to the terminal device. If the block ID does not match after an error occurs after being transmitted to the terminal 100, the terminal device 100 sends a backup data reception rejection response (NACK) via the network 300 as indicated by reference numeral B14. The data is transmitted to the data backup server 200.
In response, the data backup server 200 closes the backup data file as indicated by reference numeral B15.
This completes the restore reading process due to the abnormal operation.

  In the above-described embodiment, the network 300 is described as providing an Internet connection service. However, the network 300 is not limited to this, and may be a network such as a local area LAN and may constitute an intranet.

  Thus, according to the present invention, the backup data is packetized using the CPU surplus power of a terminal device such as a personal computer, transmitted to the data backup server via the network, and stored in the data backup server. To provide a data backup system that receives backup data packetized from a data backup server as needed via the network and enables easy reconstruction in the event of a terminal device failure. Can do.

It is a block diagram which shows the structure of one Embodiment of the data backup system by this invention. It is a block diagram which shows the structure of the terminal device in the data backup system of FIG. It is a flowchart which shows the control operation of the terminal device in the data backup system of FIG. It is a flowchart which shows the control operation of the data backup server in the data backup system of FIG. 3 is a time chart showing a data write control operation at the time of backup in the data backup system of FIG. 1. 3 is a time chart showing a data read control operation at the time of restoration in the data backup system of FIG. 1.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Data backup system 100 Terminal device 101 User identification information 102 Password 103 Terminal specific information 110 Control part 120 Storage device 130 Network interface 140 Functional module 141 Service start command 200 Data backup server 210 Interface part 220 Service determination part 230 Terminal information database 240 Data processing unit 250, 260 Storage device 300 Network

Claims (6)

The backup data sent from the terminal device via the network is received by the data backup server and stored in the storage device. When the data backup server receives a restore request from the terminal device, it supports the terminal device. In a data backup system that transmits backup data to the terminal device via a network,
The terminal device performs operations related to data backup autonomously in the background of normal operation,
The terminal device and the data backup server send and receive backup data in a predetermined data size,
The terminal device is registered in advance with the data backup server and is given terminal identification information and a password. When the backup or restore service start command is transmitted to the data backup server, the terminal identification information and password are also stored. Send
When the data backup server receives a service start command from a terminal device, the data backup system determines whether or not the terminal device can be serviced by collating terminal identification information and a password that are sent simultaneously. .   2. The data backup system according to claim 1, wherein the predetermined data size is selected so as not to give a burst load to the buffering resources of the network.   3. The data backup system according to claim 1, wherein the predetermined data size is determined between the terminal device and the data backup server at the start of transmission / reception of backup data.   4. The data backup system according to claim 1, wherein the predetermined data size is changed between the terminal device and the data backup server in the middle of transmission / reception of backup data.   The data backup system according to any one of claims 1 to 4, wherein the terminal identification information is terminal-specific information of a terminal MAC address and an assigned IP address.   6. The data backup system according to claim 5, wherein the terminal identification information includes user identification information such as a user identifier of a user who operates the terminal device.

Images